Only use data that anyone can access in the dev workspace

[archiewood]

Feature Description
In the development workspace today, we have a mixture of queries that reference different data sources. Some of this is by design (eg when testing different database types) but mostly this is incidental.
Importantly, developers who are not part of the core Evidence team, do not have access to the BiqQuery database.

Suggest short term:

• Move all queries in spec to use local DuckDB (full support for types etc)

Longer term:

• May make sense to not require queries to produce data, but data objects that are the same as the outputs from queries. Though I'd be slightly worried that this would be less good at catching bugs, for example if we change the data format.

Goal of Feature
All developers have parity in dev experience without needing access to Evidence data warehouse credentials.

[hughess]

I think a pretty large % of the queries in there now are manually defined with unions, so just putting a duckdb file in the repo might get us most of the way there.

[archiewood]

Agh got a really long way here and then realized that Vercel + DuckDB = Bad

Workaround here would be to switch to Netlify for dev workspace. Think this is probably the easiest path forwards.

[archiewood]

Okay I've pinged it up on netlify and it works.

Proposal: we move evidence-development-workspace from Vercel -> Netlify, at least until we resolve that issue

[archiewood]

Okay for now I have:

• Removed any BigQuery queries
• Replaced the queries with DuckDB queries
• Changed the deploy target to Netlify: https://evidence-development-workspace.netlify.app
• Adjusted the UI tests to run against that new site (or the deploy preview for that site)

Things we could consider in the future:

• A build:strict on the deploy preview, such that any failing queries throw.
• This would require removing any components with error states from the deploy preview, so we'd need a different way to test these

[mcrascal]

Implemented in #809