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 follows combined optimizer PR #9196. GitHub's native stack still records the former vortex-plan-optimizer branch as this PR's base and does not expose an API for removing the closed #9166 entry. Both vortex-plan-optimizer and vortex-plan-rules point to the same combined commit (e21444ddff), so this PR's effective diff contains only ZonedPlan.

Scope

This PR only represents the physical zoned layout. A later optimization can directly match (Eval, Zoned): the generic stats rewrite produces abstract bound StatFn expressions, and the zoned rule can replace the transparent data plan with zone-backed pruning state. No additional plan-node type is required, and execution remains independent of this node definition.

Checks

• RUSTC_WRAPPER= cargo test -p vortex-layout plan::
• RUSTC_WRAPPER= cargo clippy -p vortex-layout --all-targets --all-features -- -D warnings
• cargo +nightly fmt --all -- --check
• git diff --check

[codspeed-hq]

Merging this PR will improve performance by 23.03%

⚡ 2 improved benchmarks
✅ 1960 untouched benchmarks
⏩ 89 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	in_place_non_nullable[65536]	65.6 µs	49 µs	+33.74%
⚡	Simulation	cold_misaligned[(64, 256)]	5 ms	4.4 ms	+13.18%

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing vortex-plan-zoned (8798f72) with vortex-plan-optimizer (956389d)}

Footnotes

1. 89 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. ↩