Clarify feature level requirement which have no derived component level requirement

### What

Currently there are some feature level requirements existing, which do not have any derived component level requirement.

For details see corresponding appendix d [here](https://github.com/etas-contrib/score_lifecycle/blob/feature/integration_test_report/tests/integration/integration_test_coverage.md#appendix-d--feature-requirements-with-no-derived-component-requirement-20).

On the other hand, there are feature level requirements with many component requirements derived. See appendix e [here](https://github.com/etas-contrib/score_lifecycle/blob/feature/integration_test_report/tests/integration/integration_test_coverage.md#appendix-e--feature-requirements-and-their-derived-component-requirements)

These requirements should be clarified in our regular meeting:
- Is it fine that these have no component level requirement?
- What happens if later on a component level requirement is introduced, but there is a test which already "fully verifies" the feature level requirement?
- Is there something like an "ideal number" of linked component requirements? So is it fine that two feature level requirements are used as a basis for ca. half of our component level requirements?

### Acceptance Criteria (DoD)

TBD

### How

_No response_

Start with tests/integration/integration_test_coverage.md, especially Appendix D and Appendix E. Bring the three listed questions to the regular meeting and document the decisions about unlinked feature requirements, later component requirements, and the expected number of links. Done requires agreed acceptance criteria replacing the current TBD.

Written by the indexing model from the issue text.