[Concept] Forwarding of notifications

**As** Trace-X
**I want** forwarding of notifications in case of alerts and notifications
**so that** a quality incident could be forwarded app supported through the supply chain respecting the data sov

## Acceptance Criteria
- [ ] Concept created of handling forwarded notification
- [ ] Supporting forward of quality notifications over the trace-x frontend
- [ ] Received quality investigation could be forwarded to customer or supplier respecting the direction the incident was reported in the supply chain (upwards / downwards)
- [ ] Meta information from inital quality notifications are used for the forwarded quality notifications
- [ ] Meta information of forwarded notifications could be overridden by supervisor
- [ ] Forwarding notification requires role supervisor
- [ ] In case of forwarding notification based on affected part of customer, a new selection of affected part for supplier must be possible. OEM reports on a gearbox of a vehicle - the gear is the affected part of the forwarded notification.
- [ ] User is able to comprehend the relationship between received notification (OEM) and forwarded notification (Supplier)
- [ ] In case the supplier accepts or declines a forwarded notification, this could be forwarded via the initial notification received from OEM level
- [ ] The app persists and visualize the relationship between notifications and forwarded notifications this relationship could be used to report back information of forwarded messages from tier levels
- [ ] State diagram is updated

## NFR
- Data Sov is guranteed

## Hints / Details
- https://miro.com/app/board/uXjVO5JVoho=/?moveToWidget=3458764586654959964&cot=14
- https://github.com/eclipse-tractusx/traceability-foss/discussions/713

## Out of Scope

- ...

Start by reviewing the linked Traceability discussion and Miro board, then examine the current state diagram referenced in the acceptance criteria. Define the forwarding concept, notification relationships, role and data-sovereignty constraints, and frontend behavior before implementation. Done should include an updated state diagram and agreement on the broad acceptance criteria.

Written by the indexing model from the issue text.