Update deps and switch to ES modules

[mike-marcacci]

This has ended up becoming more substantial than originally intended. Several dependencies were abandoned or went completely different directions with major breaking changes.

This PR makes the following changes, many of them broken out into isolated commits when possible:

• [x] update all outdated dependencies
• [x] update build output to use ES modules
• [x] drop yarn in favor of npm, now that yarn has diverged and npm has workspaces
• [x] replace abandoned or divergent dependencies with maintained ones (graphql-request to react-query, etc)
• [x] make UI components static to keep typical "build time" dependencies from having production security implications
• [x] move end-to-end tests to an "example" project, rather than the root
• [x] add authenticated GraphiQL to the example project
• [x] ensure example/test keys are generated and not committed
• [x] adopt the devcontainer spec
• [x] ensure development is refined using docker-compose
• [x] ensure automation is working as intended
• [ ] write docs for running the example

I explicitly avoided making substantial changes to the API or business logic – the purpose of this PR is strictly to bring this codebase up to date.

[mike-marcacci]

Note that complaints of "duplication" are primarily because tests and other high-duplication files were moved, causing them to be seen as "new code" by SonarCloud. We should ignore that gate for this PR.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
8.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[nickcarenza]

These changes look good to me. It's strange that sonar is categorizing moved code as duplication.

[mike-marcacci]

Thanks @nickcarenza! Just to clarify Sonar's behavior: it already considers this code as duplicate in main, but normally only reports on changes during PR scans, and because I moved them it considers them changed.