feat(query): execute authoritative QueryPlan

[zzylol]

Summary:

• Compile an authoritative physical QueryPlan from ASAPPlanner post-ASAP IR using canonical Planner SummaryFamilyType values.
• Represent serving plans as stable node-ID DAGs; preserve shared nodes, validate roots/edges/cycles/reachability at activation, and execute in memoized topological order.
• Bind every ReadMaterialization node to an exact policy fingerprint plus metric, stored SID layout, output grouping, and window. Family semantics remain authoritative in BackendPlan/Planner types rather than being duplicated in the binding.
• Production serving resolves fingerprint -> SID and performs exact metadata integrity checks; it does not reconstruct Planner IR or run serving-time candidate search.
• Publish QueryPlan atomically with PrecomputePlan and BackendPlan; typed misses fall through to the archive backend.
• Reject unsupported window candidates until an executor advertises complete physical evidence and accuracy semantics.

Verification:

• cargo check --locked -p control_plane -p data_plane
• cargo test/clippy compile all targets
• git diff --check
• GitHub MVP backend CI

Stack 1/12. Later PRs target this branch; merge in stack order.

[zzylol]

Updated for the clarified Planner/window ownership contract in ASAPCollector main (docs PR #586): pinned ASAPPlanner window-framework API at 264937e (Planner PR #331), added complete workload-scoped physical implementation evidence, let Planner select the abstract SummaryWindowFramework, retained the concrete implementation identity downstream, and fail closed on missing/stale/incompatible evidence. The rest of the backend stack was rebased on this boundary.