Feature Request: vendor in pyodide build

[NickCrews]

See duckdb/duckdb-pyodide#7

cpcloud added a build recipe for building a pyodide version of duckdb to the duckdb/duckdb repo in 2024 and maintained it through mid 2025, but it didn't survive the migration when duckdb/duckdb-python split out of duckdb/duckdb. Then, in Feb of this year, the pyodide recipe was switched to depend on wheels built by the xlwings/duckdb-pyodide repo.

Depending on the fork is both dangerous (who is that person?) and not stable. That pyodide-recipes recipe includes a sha256 so we can be sure that the binary won't change under us, but I'm not sure anyone actually ever did the due diligence to try building using that fork and verifying that the included .whl actually matched the claimed sha256.

I would like to see the pyodide wheels built by an official duckdb repo. I feel like this duckdb-python one is probably the right place. What would need to happen for that to be possible? I figure should be pretty easy to get claude to port over that fork into this repo, the harder part I can't do is have the taste to figure out what parts of the pattern should get adapted.