duckdb: COPY TO s3 uri

[myrrc]

Allow writing to S3 for vortex-duckdb.

Resolves: #9380

[codspeed-hq]

Merging this PR will degrade performance by 0.9%

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

⚡ 1 improved benchmark
❌ 1 regressed benchmark
✅ 1992 untouched benchmarks
⏩ 89 skipped benchmarks¹

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	cold_misaligned[(64, 256)]	4.4 ms	5 ms	-12.89%
⚡	Simulation	take[small_m/shuffled/primitive/nonnull/chunks=16384/indices=16]	1.2 ms	1 ms	+12.73%

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-write-s3 (3da25fb) with develop (f8d4db9)}

Footnotes

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

Does this have any tests?

[myrrc]

Does this have any tests?

We don't have s3 tests in general, but I have a TODO item on adding them via minio.
So far I've tested it locally.