Requirements Engineering ML3

### Epic Description

Get the Requirements Engineering from ML2 to ML3
- First the gaps in the process according to the definition in https://eclipse-score.github.io/process_description/main/ have to be documented in below list
- [x] deployment of process in one S-CORE module/platform repo, all documents are valid
- persistency: has stkh, feature, aou, component req and feature inspection - missing component inspection (see below sub-issue)
- baselibs: has stkh, feature, aou, component req and component inspection - missing feature inspection and completion of component inspection (see https://github.com/eclipse-score/baselibs/issues/245)
- [ ] process requirements prio 1&2 "automation" are implemented in tooling
- gd_req__req_attr_impl - see https://eclipse-score.github.io/docs-as-code/main/internals/requirements/requirements.html#tool_req__docs_dd_link_source_code_link
- gd_req__req_attr_testlink - see https://eclipse-score.github.io/docs-as-code/main/internals/requirements/requirements.html#tool_req__docs_test_link_testcase
- gd_req__req_attr_version
- gd_req__req_suspicious - it became clear that the requirement process shall be simplified to be able to remove the use of "requirement covered" attribute.
- gd_req__req_linkage_architecture_mandatory - make sure satisfied_by link gets mandatory
- [ ] respective tool evaluation done
- https://eclipse-score.github.io/score/main/score_tools/tools_documentation/doc_as_code.html#doc_tool__doc_as_code
- [ ] Safety Audit passed (no open deviations/actions)
- Action_8 about the hash tool / change impact analysis tool

### Acceptance Criteria (DoD)

all identified gaps have been resolved