add vortex-geo crate and WKB extension type

[a10y]

Summary

Part of the implementation of #7686

This PR adds a new crate, vortex-geo, which will hold all extension types, custom layouts, and encodings necessary to store geospatial vector datasets in Vortex files.

The goal of this crate is to enable integration with DuckDB Spatial, GeoDataFusion, SedonaDB, and Iceberg v3 geo types.

This initial PR implements an extension type for the Well-Known Binary encoding (WKB). This encoding is the most common format for geospatial data for analytics, it's what both GeoParquet and DuckDB use to represent geometry types.

We also wire this into vortex DuckDB extension to support converting Geometry columns between Vortex and DuckDB formats.

API Changes

Adds new crate vortex-geo with extension type WellKnownBinary, (geo.wkb)

Adds support for geometry columns to DuckDB as well, e.g. you can now do something like

SELECT building_id, building_name, ST_Area(geometry) AS area 
FROM read_vortex("buildings.vortex")
ORDER BY area DESC
LIMIT 10;

It won't be very performant yet, not until we support better layouts + stats for geometry.

Testing

We have unit tests for metadata serde, round trip conversion between Vortex <> DuckDB geometry format, and an additional E2E test that demonstrates reading a Vortex file with geometry data and providing it to the DuckDB Spatial extension.

[codspeed-hq]

Merging this PR will degrade performance by 24.94%

⚠️ 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 regressed benchmark
✅ 1168 untouched benchmarks
⏩ 138 skipped benchmarks¹

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Simulation	new_bp_prim_test_between[i64, 32768]	177.3 µs	236.2 µs	-24.94%

---

_{Comparing aduffy/geo-v0 (134b470) with develop (5e5572b)}

Footnotes

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

[a10y]

These C++ changes are because DuckDB upstream doesn't expose the full geometry type stuff over the C API.

[a10y]

Claude generated this function and the header update, most of the rest of the PR was braincoded

[a10y]

in certain situations this could lead to UB depending on the allocator, b/c if duckdb_malloc returns NULL then you'd call slice::from_raw_parts(NULL) which is UB.

see the new take_blob function below

i only fixed this b/c i was going to repeat this for the GEOMETRY branch and figured i'd fix it in both places instead

[a10y]

these methods should've always been &mut for soundness reasons, they were just missing before

[a10y]

see this for (rather simple) example of querying geometry data from DuckDB