Rewrite the app to use static frontend deployment with DuckDB-WASM

[shippy]

It's a little silly that we have a three-step deployment for what's essentially a simple database query.

• There's nothing dynamic about the frontend; it should be in a CDN, not a container.
• There's very little dynamic about the backend; it just connects to a database, and we can do that with DuckDB-WASM (npm).
• The database prep run needs to happen, but the result could in theory sit in S3/Cloudfront/any other CDN, since it doesn't contain private information. (And the process could be simplified with some drop site that we put updated SQL dump into, but that's outside of the scope of this issue.)

This could be an interesting research project for investigating the new Cloudflare functionalities (Durable objects etc.) - I'm not sure they fit in, though, since the end result really could be a simple S3 deployment.

To do:

• Create a detailed plan
• Set up Cloudflare/S3 credential access
• Add frontend functionality that uses duckdb-wasm to directly query a adk-wrapped.duckdb object deployed alongside the built frontend
• Determine if any additional steps are necessary

[shippy]

Note: currently, duckdb-wasm has some trouble loading the generated DuckDB 1.3.0 file, so might need to export that one table as parquet and load that