chore: update to process 2.0.3

[a-zw]

No description provided.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 6a111c60-b6b2-4538-b5aa-671ca31ce61b
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 5.638s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

Documentation preview for this pull request is available at:
pr-694: https://eclipse-score.github.io/docs-as-code/pr-694/

[AlexanderLanin]

Root cause: integration race between #684 and #676

The score_process 2.0.3 update is not the functional cause of this failure. The failure is an integration race between two independently merged changes:

1. feat: optional conf.py #684 changed the docs() contract: when docs/conf.py is absent, callers must provide both project and project_url.
2. feat: add opt-in cross-module compatibility warnings #676 added score_docs_compatibility_fixture, which calls docs(source_dir = "docs") without a docs/conf.py, project, or project_url.

Each change can pass CI against its own base: #684 has no such fixture, while #676 was compatible with the previous docs() behavior. Once the Merge Queue / synthetic PR merge combines both changes, the fixture violates the new contract. docs() fails during analysis before :docs_bundle is declared; the later no such target …:docs_bundle messages are follow-on errors.

This PR is where the combination became visible because its checks ran against GitHubs synthetic merge ref (refs/pull/694/merge) with the current base branch. Thus the queue/merge-result test exposes the race; it is not itself the root cause.

Fix: update src/tests/docs_bzl/cross_module_fixture/BUILD to pass project and project_url, or add docs/conf.py.