Streamline Release Process documentation

[SebastianBezold]

Description

Topic to be covered

• Website "Versions" nav item (needed?)
• Process definition in Tractus-X (issues labels responsible persons)
• Remove duplicate descriptions (sig-release vs. tractus-x-release, website)
• How does Tractus-X support the Association process?
• Find consensus in committer group (mailing list, and/or matrix committer room + "sounding meeting")

Additional info

• docs: add initial release process description skeleton #519
• https://github.com/eclipse-tractusx/tractus-x-release/blob/main/RELEASE.md
• https://eclipse-tractusx.github.io/release-information

FYI @stephanbcbauer

[RolaH1t]

working assumption @stephanbcbauer & @RolaH1t (21-Mar):
Release-Info must be available in TWO locations:

1. highlevel intro and "pick-up" of users on homepage (github.io page)
2. SIG Release repository => here with all details
   note: current info available in "Tractus-X release" repo will be checked and if applicable will be moved to SIG release

[RolaH1t]

consolidation approach aligned with @stephanbcbauer and @Siegfriedk (TX project leads):

Detailed text building blocks will follow

[RolaH1t]

Thanks to @Siegfriedk this issue can be closed as resolved, once the following PR`s are merged:
eclipse-tractusx/tractus-x-release#26
eclipse-tractusx/eclipse-tractusx.github.io#852
#662

[SebastianBezold]

Hey @RolaH1t and @Siegfriedk,

to be honest, I would have appreciated, if you had based your work on top of #519. There has been a lot fo effort put in, not only by me, but also by other contributors (@evegufy, @jzbmw, @HFocken) adding comments to improve the contents.