VortexSession API cleanup pass

[AdamGS]

Summary

This PR makes the final pass to make the VortexSession immutable, removing the to_builder function and trying to clear up all call sites.

I've also tried to find all docs referencing it, but the change touches so many places I might've missed something.

One big change here is changing array_session (which I think I introduced?) to default_session_builder

[codspeed-hq]

Merging this PR will not alter performance

⚠️ 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.

⚠️ 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

⚡ 2 improved benchmarks
❌ 1 regressed benchmark
✅ 271 untouched benchmarks
⏩ 1319 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	slice_empty_vortex	310 ns	368.3 ns	-15.84%
⚡	Simulation	bitwise_not_vortex_buffer_mut[128]	244.4 ns	215.3 ns	+13.55%
⚡	Simulation	bitwise_not_vortex_buffer_mut[1024]	304.7 ns	275.6 ns	+10.58%

Tip

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

---

_{Comparing adamg/session-new-api-pass (70756d4) with develop (b4c85b6)}

Footnotes

1. 1319 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]

We want shorthand methods for the builders as well so we don't have to use get_mut::<T>()

[robert3005]

I missed the part where this makes it difficult to add things at runtime and will force to teach consumers about unloading. Unloading can be difficult since you need to track all the state that you have borrowed from the session