feat(cuda): support column projection and dictionary decoding in file scans

[0ax1]

Summary

• Add column projection to CUDA scans, avoiding reads and decoding for unselected columns.
• Decode dictionaries for consistent Arrow stream schemas, preserving defaults for other exports.
• Cache schemas without reading a batch.
• Preserve row-block boundaries, register the CUDA layout edition, and generate the C header.

[codspeed]

Merging this PR will regress 1 benchmark

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

⚡ 3 improved benchmarks
❌ 1 regressed benchmark
✅ 2243 untouched benchmarks
⏩ 176 skipped benchmarks¹
🗄️ 1 archived benchmark run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	WallTime	arrow_checked_add_u32_neon[16384]	12.9 µs	20.4 µs	-36.55%
⚡	Simulation	decompress[u64, (4000, 1024)]	87.1 µs	71.6 µs	+21.78%
⚡	Simulation	allocate_drop_bytes[0]	635.5 ns	527.2 ns	+20.55%
⚡	WallTime	filtered_sink_i64_avx2[OneNullInEight]	26.2 µs	23.3 µs	+12.4%

Tip

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

---

_{Comparing ad/cuda-projected-file-scans (744abf1) with develop (75b6225)}

Footnotes

1. 176 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. 1 benchmark was run, but is now archived. If it was deleted in another branch, consider rebasing to remove it from the report. Instead if it was added back, click here to restore it. ↩