analysis/tracing: add canary requirement and test links

[Nikhil2206]

Summary

Author the missing analysis/tracing component requirement and link all 24 canary wrapper tests to it.

The requirement covers canary-protected data integrity: wrapping arbitrary data with configurable canaries, detecting corruption at either boundary, and reporting corrupted data as unavailable.

Changes

• Added comp_req__analysis_tracing__canary_protected_data_integrity.
• Added the analysis/tracing documentation bundle and root component wiring.
• Added required RecordProperty metadata to all 24 canary wrapper tests.
• Covered nominal construction/access, 32-bit and 64-bit canaries, layout, copy/move state propagation, and injected start/end/both-canary corruption.

Validation

• bazel test --config=bl-x86_64-linux //score/analysis/tracing/common/canary_wrapper/test:canary_wrapper_test -> passed.
• bazel build //score/analysis/tracing:docs -> passed.
• bazel run //:format.fix -- ... -> completed successfully.
• git diff --check -> passed.
• Confirmed 24 test declarations and 24 linkage properties.

The full bazel run //:docs command is blocked before Sphinx validation by the pre-existing root-owned _build/ permission error. The component docs bundle itself builds successfully.

Traceability

All tests use PartiallyVerifies, Description, TestType, and DerivationTechnique. Deliberately corrupted canary tests use fault-injection; boundary-validity cases use boundary-values.

The requirement derives from feat_req__com__data_corruption[version==1], which requires protection against corruption of data consumed by higher-criticality partners.