EPIC: Rework detail design process

[RolandJentschETAS]

The detail design process must be reworked:

See https://github.com/orgs/eclipse-score/discussions/2234#discussioncomment-15547087

Modify meta model (within docs as code repository) and process description (within process repository) for:

• In the detail design the sphinx needs elements for SW_Units shall be removed or only mandatory for future ASIL D development.
• Also remove "Real Arc Interfaces" from sphinx needs model
• Also the sphinx needs objects for SW_Unit test shall be removed
• The software architecture design shall get rid of the definition of software logic and real interface operations. At least make it optional (could be also allocated or refer to detail implementation)

and Unit Tests as Sphinx needs

Background is, that ISO26262 does not requests this for ASIL_A/B and hold on that will create an overwhelming effort (=over engineering)

[OliverHeilwagen]

Please also consider the process demands for static detailed design (dd_sta), and dynamic detailed design (dd_dyn).

For C++ static detailed design it should be allowed to fetch the content via doxygen, remove the need for manual sync of sphinx dd_sta and implementation. (Rust approach tbc.)

Sphinx dd_dyn objects should not be mandatory, consider thin adapter classes. At least the following variation should be tolerated by the process:

• simple dynamic detailed design: document along with the static detailed design class/methods description (doxygen).
• complex dynamic detailed design: document as dedicated sphinx objects (dd_dyn) e.g. state machine overview