Update dependency score_process to v2

[eclipse-score-bot]

This PR contains the following updates:

Package	Type	Update	Change
score_process	bazel_dep	major	1.5.4 → 2.0.0

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by #infrastructure automation. Contact us if you have any questions or feedback.

[eclipse-score-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel.lock

Command failed: bazel mod deps --lockfile_mode=update
 no actions running
ERROR: score_docs_as_code@4.0.1 depends on score_process@1.5.3 with compatibility level 1, but <root> depends on score_process@2.0.0 with compatibility level 2 which is different

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

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

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 86525e28-08dc-4fd8-813e-c5444fd9e50a
Computing main repo mapping: 
ERROR: Error computing the main repository mapping: Missing checksum for registry file https://raw.githubusercontent.com/eclipse-score/bazel_registry/main/modules/score_process/2.0.0/MODULE.bazel not permitted with --lockfile_mode=error. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile.