Set valid_from attribute for all features

[antonkri]

What

Adds :valid_from: v1.0.0 to feat_req entries (where not already set) for the following features, and to the stakeholder requirements they are linked to via derived_from:

• baselibs (already set — no changes)
• logging (analysis-infra/logging)
• communication (main, ipc, some_ip_gateway)
• config_management (configuration/config_mgmt)
• persistency
• lifecycle
• time
• diagnostics (already set — no changes)
• security_crypto (crypto)

Details

• 289 feat_req insertions across the feature requirement files.
• 44 stakeholder requirement insertions in docs/requirements/stakeholder/index.rst (only the stkh_req entries referenced by the above features' derived_from, and only where valid_from was missing).
• Placement follows existing conventions: after :version: for feat_req; as the last field (after :tags: where present) for stkh_req.
• Entries that already had valid_from were left untouched.

Notes

• No "network management (nm)" feature exists in the repo, so it was skipped.
• Total: 333 insertions across 10 files.

Verification

• bazel run //:docs builds successfully; schema validation passes with 0 warnings.
• The 6 non-fatal traceability warnings in lifecycle are pre-existing (verified by rebuilding against the base without these changes) and unrelated to this change.

[github-actions]

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

[umaucher]

+1 for persistency

[S-MOHAMD]

for lifecycle requirements, The feature requirements are to be reduced in PR #3068 . these 2 PR's are dependent to each other