Epic: OS / QNX integration process

*Acceptance Criteria:*

Process how to integrate QNX defined:
- [ ] How is QNX (or any other OS) integrated in our architecture (views)
- consider the OSAL as part of Baselibs (talk to @4og, component doc: https://eclipse-score.github.io/score/main/modules/baselibs/os/docs/index.html, "detailed design" is in https://github.com/eclipse-score/baselibs/blob/main/score/os/README.md)
- rework https://eclipse-score.github.io/score/main/modules/os/docs/index.html
- [x] Which safety features and safety mechanisms do we need/expect?
- Safe C++ Lib, Safe Math Lib, Safe filesystem, Safe privileges, Safe OS startup, Process memory protection (incl. stack), Safe DMA, Safe HW configuration protection
- But we will not integrate the "safe" QNX in S-CORE, so these safety features/safety mechanisms could only be given as an AoU to the OS
- [x] Can we directly use the AoU from QNX safety manual and import?
- no, QNX safety manual will not be available, list of qualified QOS and C++ elements is available in the open, see e.g. https://fs-products.tuvasi.com/certificates?keywords=Blackberry&productcategory_id=1#prodid_9842
- what documentation is provided with the "free for non-commercial use" QNX version?
- [x] Do we need to hide the AoUs?
- no, we do not provide at all, perhaps do as in comment below
- [x] Do we want to derive S-CORE "AoU" requirements from QNX ones (e.g. using only the restrictions not recommendations)
- yes, for the most important ones like no use of "root" privilege
- [ ] Also (QCC) compiler has to be taken care for - what compiler do we use? Tool evaluation?

*Prerequisites:*

Clarified Licensed use of QNX safety manuals : not possible for S-CORE