Add e2e tests for happy paths

[jeddy3]

Which issue, if any, is this issue related to?

Closes #512

Is there anything in the PR that needs further explanation?

A couple of things to note:

• the tests run in sequence to speed things up, as the initial server start takes a while
• there are a few workarounds because of how Monaco works, including using element names to locate the key parts of the app

You can use npx playwright test --ui locally to see the traces of the tests.

[netlify]

✅ Deploy Preview for chimerical-trifle-8d3c21 ready!

Name	Link
🔨 Latest commit	d3ea07a
🔍 Latest deploy log	https://app.netlify.com/projects/chimerical-trifle-8d3c21/deploys/69259b6bd3245800086da4e1
😎 Deploy Preview	https://deploy-preview-513--chimerical-trifle-8d3c21.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ybiquitous]

Thank you, I love the E2E addition. 👍🏼

Overall LGTM, but I've left a few minor comments.

[ybiquitous]

Great. I've confirmed the uploaded HTML test report. LGTM 👍🏼

---

By the way, it seems a good practice to add e2e to status checks in the branch ruleset:

(it's not a blocker for this PR, though)

[jeddy3]

Thank you for the review 🙇

---

By the way, it seems a good practice to add e2e to status checks in the branch ruleset:

Done.

---

I remembered to remove the bot from the commit message:

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>

It was added by this commit.

[ybiquitous]

I remembered to remove the bot from the commit message:

This is pretty hard to notice. Let's not mind too much (I might fall into the hole, too). 😅