Playground broken in 0.8.1

[max-sixty]

What's up?

As reported by @richb-hanover in #2512

I've spent a couple of hours on this but to no avail. The main problem is that it works locally! Run task run-web or task run-playground — works fine. I get a couple of warnings:

Could not create web worker(s). Falling back to loading web worker code in main thread, which might cause UI freezes. Please see https://github.com/microsoft/monaco-editor#faq [simpleWorker.js:20:16](http://localhost:1313/playground/playground/static/node_modules/monaco-editor/esm/vs/base/common/worker/simpleWorker.js)
You must define a function MonacoEnvironment.getWorkerUrl or MonacoEnvironment.getWorker

Then on the live playground the console gives:

FAIL WITH: Error: Range request for https://prql-lang.org/playground/playground//data/chinook/playlist_track.csv failed with error: Error: Range request for https://prql-lang.org/playground/playground//data/chinook/playlist_track.csv did returned non-success status: 0 """ [duckdb-browser-eh.worker.js:11:13975](https://cdn.jsdelivr.net/npm/@duckdb/[email protected]/dist/duckdb-browser-eh.worker.js)
Uncaught (in promise) Error: Invalid Error: Error: Range request for https://prql-lang.org/playground/playground//data/chinook/playlist_track.csv failed with error: Error: Range request for https://prql-lang.org/playground/playground//data/chinook/playlist_track.csv did returned non-success status: 0 """
    runQuery https://cdn.jsdelivr.net/npm/@duckdb/[email protected]/dist/duckdb-browser-eh.worker.js:11
    onMessage https://cdn.jsdelivr.net/npm/@duckdb/[email protected]/dist/duckdb-browser-eh.worker.js:10
    onmessage https://cdn.jsdelivr.net/npm/@duckdb/[email protected]/dist/duckdb-browser-eh.worker.js:24

...but the file at https://prql-lang.org/playground/playground//data/chinook/playlist_track.csv does exist.

FWIW this increases my confidence that we made the wrong call in #1507 — without this we would have spotted this much closer to the offending commit. The backport fails regularly enough that it's easier to just release a new version. I again update my beliefs that almost anything that increases maintenance burden is not worthwhile.