fix(planner): make BackendPlan authoritative for warm execution

[zzylol]

Summary

• replace the legacy ASAP-tier analyzer with ASAPPlanner post-ASAP planning
• resolve each SummaryAgg against exact BackendPlan materializations before SID lookup/DAG execution
• fail closed on filter, grouping, window, family/parameter, route, and generation mismatches
• remove legacy UNSET-fingerprint authorization and arbitrary first-family selection
• publish streaming config, BackendPlan, and storage routing through one atomic PhysicalPlan API
• strengthen BackendPlan validation and add generation fencing
• make PhysicalCompiler consume post-ASAP IR and retain an explicit planner adapter

Validation

• cargo check -p control_plane -p data_plane
• cargo test -p control_plane --bin control_plane
• cargo test -p control_plane emit::backend_push::tests --lib
• cargo test -p control_plane backend_plan --lib
• cargo test -p data_plane post_asap --lib
• cargo test -p data_plane storage_engines::types::hot_reload_config --lib
• persistence index tests pass serially (parallel full-suite run exposes existing timing flakes)

Stacked on #469.