feat(control-plane): migrate to latest ASAPPlanner IR

[zzylol]

Why

Physical compilation for the MVP must use the current ASAPPlanner IR rather than the older sketch, reduction, grouping, and maintenance contracts.

What

The control plane and data plane migrate to the latest Planner types and normalized capabilities; unsupported TopK selections remain fail-closed.

How

Update pinned Planner revisions and adapt selection, cost, lowering, allocation, emission, and backend execution code to the current typed IR.

Before this PR

The backend was pinned to an incompatible Planner revision and could not consume current Planner selections.

After this PR

The existing optimization and execution pipeline compiles against current Planner types while rejecting selections the runtime cannot safely execute.

Evidence

Execution evidence is the passing backend workspace test suite against the updated Planner pin. Visual and performance evidence are not applicable.

Verification

• Unit/integration tests: inherited workspace and control-plane suites were run during this stack's implementation.
• End-to-end behavior: unsupported TopK remains fail-closed in selection tests.
• Other checks: control-plane compilation and formatting passed.

Architectural decisions

This is an interface migration, not a parallel compatibility layer. Runtime capability checks remain explicit.

Limitations and follow-up

Stacked on #449. The typed physical compiler is added separately in #451.

Human review — do not complete with an agent

• The MVP boundary is correct.
• New conceptual layers or public interfaces are necessary.
• The before/after description matches the intended product behavior.
• Human reviewer:
• Decision and rationale: