Add lifecycle correlation and bounded OTLP tracing

[ostapondo]

Summary

• add typed identifiers for observation, incident, occurrence, analysis, plan, repair transaction, and verification scopes
• propagate identifiers through incident and analysis JSON, observation journal, structured logs, repair receipts, timeline ledger, TUI, and read-only MCP output
• add an explicit opt-in, bounded OTLP/HTTP trace exporter with a reviewed lifecycle-span allowlist
• keep tracing disabled by default and exclude paths, arguments, evidence, errors, and model payloads from exported spans
• ignore local graphify-out artifacts

Validation

• cargo fmt --check
• cargo test --workspace
• cargo clippy --workspace --all-targets -- -D warnings
• ./scripts/validate-logging.sh
• ./scripts/validate-observation-recovery.sh
• ./scripts/validate-mcp.sh
• ./scripts/benchmark-idle.sh 30 (avg CPU 0.040%, avg RSS 9.04 MiB)
• cargo check -p rescueloop-repair --target aarch64-pc-windows-msvc

Full Windows workspace cross-check requires a Windows C SDK for bundled SQLite/TLS and remains covered by Windows CI.