docs(lifecycle): move comp_req entries into own requirements file

[ramceb]

What

Split docs/features/lifecycle/requirements/index.rst, which mixed feat_req and comp_req entries under the same section headings, into two files:

• index.rst — now contains only feat_req (feature requirement) entries
• component_requirements.rst (new) — contains only comp_req (component requirement) entries, grouped under the same section headings

Why

Keeping feature and component requirements in one file made it hard to navigate. Separating them into dedicated files improves readability and matches the pattern already used by other modules (e.g. docs/modules/feo/feo/docs/requirements/component_requirements.rst).

Notes

• No requirement content or IDs were added, removed, or modified — verified all 95 :id: values (32 feat_req + 63 comp_req) are identical before/after, just relocated.
• No toctree changes needed: docs/features/lifecycle/index.rst already includes requirements via a glob (./requirements/*), so the new file is picked up automatically.

[github-actions]

The created documentation from the pull request is available at: docu-html

[aschemmel-tech]

seems we are doing parallel work: see #3123

[FScholPer]

Should be in the module repo

[anmittag]

@NicolasFussberger is this pr still valid or have you already moved the parts into module folders?

[NicolasFussberger]

I assume this is no longer valid, as comp_req have already been moved to the lifecycle repo.
Can you confirm this @aschemmel-tech ?

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.