refactor(array): allocate execution outputs through context

[gatesn]

Summary

Allocate execution outputs through the execution context.

Changes

• Propagate allocators through filter, take, interleave, and patches.
• Use context allocators in dictionary and scalar functions.
• Add tests for allocator propagation.

[codspeed-hq]

Merging this PR will degrade performance by 8.82%

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

⚡ 1 improved benchmark
❌ 6 regressed benchmarks
✅ 2083 untouched benchmarks
⏩ 206 skipped benchmarks¹
🗄️ 4 archived benchmarks run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	take_search[(0.005, 0.05)]	20 µs	23.1 µs	-13.7%
❌	Simulation	take_search[(0.01, 0.05)]	20.7 µs	23.9 µs	-13.26%
❌	WallTime	words_gather_scalar_avx2[65536]	8.3 µs	9.4 µs	-12.05%
❌	Simulation	take_search[(0.005, 0.1)]	26.2 µs	29.4 µs	-10.78%
❌	Simulation	take_search_chunked[(0.01, 0.05)]	31 µs	34.5 µs	-10.16%
❌	Simulation	take_search_chunked[(0.005, 0.05)]	31 µs	34.5 µs	-10.13%
⚡	Simulation	encode_varbin[(2000, 2)]	483.8 µs	437.8 µs	+10.51%

Tip

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

---

_{Comparing ngates/buffer-allocator-execution (cd00ce3) with ngates/buffer-allocator-builders (0ce40e7)}

Footnotes

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

2. 4 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩

[codecov]

Codecov Report

❌ Patch coverage is 81.06169% with 132 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.24%. Comparing base (4a232a6) to head (8df467b).

Files with missing lines	Patch %	Lines
...rray/src/arrays/filter/execute/take/fixed_width.rs	58.82%	21 Missing ⚠️
...ex-array/src/scalar_fn/fns/binary/compare/bytes.rs	75.60%	20 Missing ⚠️
vortex-array/src/scalar_fn/fns/like/mod.rs	73.91%	18 Missing ⚠️
...-array/src/scalar_fn/fns/binary/compare/decimal.rs	58.06%	13 Missing ⚠️
vortex-array/src/scalar_fn/fns/binary/boolean.rs	64.00%	9 Missing ⚠️
...ortex-array/src/arrays/filter/execute/take/rank.rs	58.82%	7 Missing ⚠️
vortex-array/src/arrays/filter/execute/take.rs	25.00%	6 Missing ⚠️
...x-array/src/arrays/interleave/execute/primitive.rs	75.00%	6 Missing ⚠️
vortex-array/src/patches.rs	70.00%	6 Missing ⚠️
...ortex-array/src/scalar_fn/fns/list_contains/mod.rs	60.00%	6 Missing ⚠️
... and 13 more

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.