Add zoned layout scan plan

[joseph-isaacs]

Summary

• add a ZonedPlan physical node with a transparent data child and auxiliary zones child
• construct it from both current vortex.zoned layouts and legacy vortex.stats layouts
• recursively optimize both child plans
• expose the node through the public plan API and new_plan dispatch
• add plan-tree snapshots for current and legacy zoned layouts

Stack

This draft is stacked on #9166 and targets vortex-plan-optimizer.

Scope

This PR represents the physical zoned layout without inventing execution semantics that the current plan IR cannot express. Zone-map pruning still needs a query-aware predicate/pruning plan and will be handled with plan execution in a later change.

Checks

• cargo test -p vortex-layout — 211 passed
• cargo clippy --all-targets --all-features
• cargo +nightly fmt --all -- --check
• git diff --check

[codspeed-hq]

Merging this PR will degrade performance by 21.36%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 1900 untouched benchmarks
⏩ 43 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	decode_varbin[(1000, 2)]	61.4 µs	78.1 µs	-21.36%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing vortex-plan-zoned (73dba37) with vortex-plan-optimizer (042e358)}

Footnotes

1. 43 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩