Release Mgt ML3

### Epic Description

Get the Release Mgt 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
- [ ] deployment of process in one S-CORE module/platform repo, all documents are valid
- Releases are done in all relevant repos, e.g. reference_integration: https://eclipse-score.github.io/reference_integration/main/s_core_v_1/releases/release_note_score_v0_7.html
- [ ] process requirements prio 1&2 "automation" are implemented in tooling
- gd_req__release_note - automatic release note generation (check with release team) ?
- [ ] respective tool evaluation done
- tbd
- [ ] Safety Audit passed (no open deviations/actions)
- "started" items resolved in https://github.com/eclipse-score/process_description/issues/558 - presentation in audit pending

### Acceptance Criteria (DoD)

all identified gaps have been resolved

Start by reading the process definition and the referenced reference_integration release note to enumerate the ML2-to-ML3 gaps. Review the release-note automation requirement and process_description issue #558, then coordinate the tool evaluation and audit follow-up. Done means every listed gap is resolved and the Safety Audit has no open deviations or actions.

Written by the indexing model from the issue text.