Update tool requriements

[AlexanderLanin]

Context
Tool requirements are based on process requirements. When a process requirement changes, the related tool requirements must also be updated. At the moment, this is a manual step with no tool support, but it is important to keep everything consistent.

Goal
Ensure tool requirements are aligned with the latest process requirements and review existing ones for correctness.

Tasks

1. Update the referenced process requirements (via MODULE.bazel).
2. Identify changes that impact tool requirements.
3. Update the tool requirements accordingly.
4. While updating, review existing tool requirements to check if they are still valid.

Acceptance criteria

• Tool requirements reflect the updated process requirements.
• Any outdated tool requirements have been corrected or removed. Missing tool requirements have been added.
• Existing structure is either applied or improved (not random new requirements in unfitting places).
• All links are updated and working.

[a-zw]

Just to note it down: Currently, it references score_process 1.1.1 while 1.2.0 is the latest.

[a-zw]

I found just one change in the process relevant for docs-as-code: Tool requirements may now satisfy stakeholder requirements (in addition to process requirements).

[a-zw]

We still need eclipse-score/process_description#172 in the meta model.