Add plan optimizer rules and push expressions

[joseph-isaacs]

Summary

• add typed PlanParentReduceRule and type-erased adapter APIs for child-driven physical-plan rewrites
• add an ordered static PlanParentRuleSet whose first successful rewrite wins
• register concrete Eval reductions for Concat, Take, RowIdx, and Pack

[codspeed-hq]

Merging this PR will improve performance by 20.44%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚡ 1 improved benchmark
✅ 1993 untouched benchmarks
⏩ 89 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	cold_misaligned[(64, 256)]	5.3 ms	4.4 ms	+20.44%

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-rules (5361eb1) with develop (15c73f3)}

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

[robert3005]

This doesn't work for nested field access since the next level is the same planid, not sure if this is handled in a follow up but you likely want to return some kind of continuation token