Use R2 bucket for duckdb libraries

[myrrc]

• Use ci-builds.vortex.dev R2 bucket as source for duckdb release and commit builds.
• Mirror release builds from duckdb github releases page. Build commits from source.
• For commit builds also try to download from R2 (useful for testing pre-release in CI)
• Gate test_geometry for duckdb under release builds only. Running it for commits means we need to bundle "spatial" extension which is hard on macos due to openssl-dev symbols

[codspeed-hq]

Merging this PR will improve performance by 19.21%

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

⚡ 6 improved benchmarks
❌ 1 regressed benchmark
✅ 1576 untouched benchmarks

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	chunked_varbinview_into_canonical[(1000, 10)]	168.9 µs	205.6 µs	-17.87%
⚡	Simulation	chunked_bool_canonical_into[(1000, 10)]	27.1 µs	16.2 µs	+67.38%
⚡	Simulation	bitwise_not_vortex_buffer_mut[128]	244.4 ns	186.1 ns	+31.34%
⚡	Simulation	bitwise_not_vortex_buffer_mut[1024]	304.7 ns	246.4 ns	+23.68%
⚡	Simulation	bitwise_not_vortex_buffer_mut[2048]	398.6 ns	340.3 ns	+17.14%
⚡	Simulation	chunked_varbinview_canonical_into[(100, 100)]	258.9 µs	223.8 µs	+15.7%
⚡	Simulation	chunked_varbinview_into_canonical[(100, 100)]	306 µs	270.8 µs	+13.01%

Tip

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

---

_{Comparing myrrc/duckdb-r2-infra (451a71e) with develop (5a764e6)}

[myrrc]

Macos deployment error:

error:  cannot create /Users/runner/work/vortex/vortex/duckdb-08e34c447bae34eaee3723cac61f2878b6bdf787/data/csv/issue2628_������.csv
        Illegal byte sequence

[myrrc]

I've verified manually this works for commits, they are uploaded and used from R2 as well.

[0ax1]

Great to see this coming into shape! Couple of questions inline. In general, will this be able to handle diff build configs: debug, release, asan etc.? The build config should prob be part of the key with which we store builds.

[myrrc]

In general, will this be able to handle diff build configs: debug, release, asan etc.?

Yes, but for the first version it won't to keep the diff small

[0ax1]

I don't love the long shell scripts and we should prob consider switching to python here eventually but let's give this a spin in prod.