Use cursor copies for PiecewiseSequence slices

[danking]

Summary

• add a shared checked cursor-copy helper for PiecewiseSequence slice gathering
• replace extend_from_slice in the primitive, decimal, VarBinView, and VarBin PiecewiseSequence consumers
• keep the safety checks explicit: each copy verifies the destination cursor range against the declared output length and capacity, and callers verify the final cursor before set_len

Validation

• cargo +nightly fmt --all
• cargo clippy -p vortex-array --all-targets --all-features -- -D warnings
• cargo bench -p vortex-array --bench listview_rebuild
• cargo bench -p vortex-array --bench cast_decimal
• cargo test -p vortex-array piecewise_sequence

[codspeed-hq]

Merging this PR will regress 2 benchmarks

⚡ 1 improved benchmark
❌ 2 regressed benchmarks
✅ 1795 untouched benchmarks
⏩ 44 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	compact[(4096, 90)]	780.3 ns	867.8 ns	-10.08%
❌	Simulation	true_count_vortex_buffer[128]	522.2 ns	580.6 ns	-10.05%
⚡	Simulation	copy_nullable[65536]	1.4 ms	1 ms	+31.91%

Tip

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

---

_{Comparing codex/piecewise-sequence-cursor-copy (87f6283) with codex/piecewise-sequence-varbin-take (5d31540)}

Footnotes

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

I think you just want here &'a mut [T] unless I am missing something

[robert3005]

ah no you need to setlen

[robert3005]

I think before we put this in vortex-buffer we would need to benchmark this against other approaches. We can keep it internal to the take impl and figure out a right abstraction from there. My suggestions were not fully tested