duckdb: vortex_version() macro

[myrrc]

Add vortex_version() duckdb function macro returning active Vortex editions. Unlike vortex release, this doesn't require fiddling with CI to propagate the release tag.

[codspeed-hq]

Merging this PR will improve performance by 20.13%

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

⚡ 6 improved benchmarks
✅ 873 untouched benchmarks
⏩ 1526 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	WallTime	arrow_checked_add_u32_neon[16384]	20.4 µs	12.8 µs	+59.79%
⚡	WallTime	arrow_checked_add_u32_avx2[16384]	21.4 µs	17.6 µs	+21.33%
⚡	Simulation	allocate_drop_arrow[0]	456.9 ns	402.7 ns	+13.45%
⚡	Simulation	allocate_drop_bytes[0]	520.2 ns	466 ns	+11.62%
⚡	WallTime	filtered_owned_i64_neon[NineNullsInTen]	28.2 µs	25.4 µs	+11.05%
⚡	WallTime	filtered_sink_i64_neon[NineNullsInTen]	28.1 µs	25.5 µs	+10.22%

Tip

Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing myrrc/duckdb-vortex-versoin (294c384) with develop (89d2f61)}

Footnotes

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

[joseph-isaacs]

This is not the vortex version.

It might be a good idea to add a enabled editions func for the writer?