Bind physical-plan execution to the authoritative SummaryCatalog

[zzylol]

The backend previously carried SummaryCatalog metadata beside parallel runtime definitions, so a successfully installed catalog did not guarantee that SummaryStore instances or QueryPlan readouts used those descriptors. BackendPlan also duplicated ownership already split across precompute, transport, and query plans.

This change completes the catalog-backed physical-plan runtime. The control plane publishes one authoritative SDS catalog snapshot; PrecomputePlan, CollectorPlan, TransmissionPlan, and QueryPlan reference stable materialization IDs; and activation installs the same snapshot into SummaryStore. New SIDs resolve shared SummaryDescriptor and DataDescriptor values from that catalog, while legacy unset identities remain an explicit compatibility path. The backend exposes observed instance inventory from registered state and real in-memory pane coverage at /api/v1/summary-inventory for lifecycle reconciliation.

BackendPlan, its protobuf/install endpoint, duplicate validation, and stale runtime code are removed. Query planning now also consumes the merged ASAPPlanner recursive value-operation DAG, preserving summary children under Sort/Limit TopK and exact binary composition. The data plane executes those nodes through catalog-bound readouts and query-time combination, while unsupported children remain Prometheus fallback boundaries.

Validation:

• cargo test -p control_plane --lib — 692 passed
• cargo test -p data_plane --lib — 1,015 passed
• cargo test -p asap_types — 63 passed
• cargo check --workspace --all-targets — passed
• cargo test -p data_plane --test backend_process_e2e --no-run — passed
• cargo fmt -p control_plane -p data_plane -p asap_types -- --check — passed