feat: promote active metadata into durable runtime

[zhouning]

Summary

• preserve the M3-19 binding schema, ledger rows, and evidence while creating a separate runtime-bound promotion candidate
• project the real Chongqing ResourceVersion into an isolated Gravitino JDBC catalog, bind stable cluster/service/StatefulSet/PVC/image identity, and prove immediate plus post-restart no-op replay
• commit path-free evidence, ADR-066, Platform Truth inventory, System-of-Record updates, and required CI coverage

Real data evidence

• ResourceVersion: a6000000-0000-4000-8000-000000000001
• content SHA-256: fd474fd65c8e4a71da241eb3fd07748ca3b972fbd2d3c32833376dbe71104007
• retained OpenMetadata UUID: 9d043410-02b5-487d-bb70-da5f3969a978
• source data and absolute local paths are not committed

Verification

• durable promotion, M3-8 JDBC restart, M3-19 reconciliation, and Platform Truth validators pass
• focused tests: 22 passed
• required platform suite: 853 passed
• Ruff and compile checks pass
• namespace, PVCs, and port-forwards are cleaned

Boundaries

This proves local JDBC/PVC restart continuity and runtime identity binding only. The candidate is not written to GDA Control. Production object storage, protected workload identity, OIDC, TLS, production ingestion, durable_catalog_verified, and production_ready remain false.

Stacked on #34. Tracks #35.