Marimo build, test, deploy workflow

[jdangerx]

Overview

Part of #19 , in conjunction with catalyst-cooperative/eel-hole#116

We need to build & store the webassembly versions of marimo notebooks somewhere, so that we can then grab them in eel-hole (see catalyst-cooperative/eel-hole#116).

What did you change in this PR?

• add stub marimo notebook in marimo/
• update existing workflow to build all .py files under marimo/ to wasm notebooks in /docs - and then deploy to GH pages
  • write a lil python script to do the grunt work here since this got gnarly in bash
  • if we want to make islands later we can do that
  • if we want to deploy the ipynbs also via nbconvert etc, we can do that in a different workflow, or add a different script to this workflow and rename it from marimo-only. All out of scope for now though.

Necessary chores to make this work:

• add uv (we could also use pixi but so far seems unnecessary? easy enough to swap though)
• set up pre-commit so we stop getting that annoying ci error.

Testing

• ran action manually, downloaded build artifact, served python3 -m http.server from artifact.
• found that you have to merge to main before we can deploy to gh-pages

To-do list

• Once approved, commit results of uv run pre-commit run -a to this branch so we get a nice green check mark, but don't clutter up these changes with those changes.

[zaneselvans]

I ran into errors when attempting to execute both the Jupyter and Marimo notebooks locally because of dependency stuff. See below.

[jdangerx]

@krivard You may want to know about this, specifically the integration testing setup, for #23 - I don't think you'll want to do super comprehensive testing of your dashboard, because that sounds both (a) hard and (b) flaky, but some basic ones to verify that things aren't crashing out is probably worthwhile.

[krivard]

Minor optional clarity notes but this looks good!

[krivard]

👍