Clarify AoU traceability and visibility

### What

Config Management needs to use the communication Assumptions of Use from [aou.trlc](https://github.com/eclipse-score/communication/blob/edaa61e1ca2e7929b6655073ea0534d92b6b652f/score/mw/com/dependability/safety_analysis/aou.trlc#L18) in its component requirements.

This functionality is supported by the [SCORE tooling AoU forwarding change](https://github.com/eclipse-score/tooling/pull/377/files). However, the required communication AoU target is currently not publicly visible to Config Management, preventing its use across repository boundaries.

Please clarify the recommended implementation that enables Config Management to consume and forward these AoUs while maintaining correct FMEA and LOBSTER traceability without duplicate processing.

### How

_No response_

### Estimates for realization

_No response_

### Category

- [ ] Affects Detailed Design

### Requirements / Architecture

- [x] Requirements / Architecture are not affected by this change?

Start with score/mw/com/dependability/safety_analysis/aou.trlc at line 18 and compare the SCORE tooling AoU forwarding change in PR 377. Determine how Config Management can access and forward the communication AoU across repositories while preserving FMEA and LOBSTER traceability without duplicate processing. Done means the recommended implementation and its traceability behavior are clearly documented.

Written by the indexing model from the issue text.