Update tool requirements

[MaximilianSoerenPollak]

📌 Description

Updating current Tool requirements to new process.
This does not convert the new process requirements into tool requirements, just changes / updates the current tool requirements according to the linked requirements.

🚨 Impact Analysis

• This change does not violate any tool requirements and is covered by existing tool requirements
• This change does not violate any design decisions
• Otherwise I have created a ticket for new tool qualification

✅ Checklist

• Added/updated documentation for new or changed features
• Added/updated tests to cover the changes
• Followed project coding standards and guidelines

[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: c347e37c-0994-4771-93b4-7da83a3750db
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
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: 10.688s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

The created documentation from the pull request is available at: docu-html

[a-zw]

Remove the "Implemented" column now that all are implemented.

[MaximilianSoerenPollak]

DOne

[a-zw]

Why the version bump? I don't see any relevant change to the requirement.

[MaximilianSoerenPollak]

The process requirement it fulfils is changed.

The question is, should that constitute a version change of the req or not?

[a-zw]

https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/requirements_concept.html#significant-requirement-changes

Updating the parent version in itself is not significant, I think. However, it is weird that the parent changes but the only (?) child does not.