Split JS into smaller files using import maps

[juliaogris]

Break up frontend code into standalone and digestable junks as precursor to web-components. Use importmaps.

Split into:

• has navigation
• evy canvas / output bindings
• evy.wasm loading
• sample loading
• easteregg
• ...

Maximise http2 usage (loads of files downloaded simultaneously).

Aim for waterfall network browser dev tools visualisation looking like this:

|--
|-
|--

Rather than this:

|--
   |-
     |--

In a follow-up step we'll implement filenames with content hashing for maximum browser caching.

The strategy has been inspired by DHH's #nobuild push:

• https://world.hey.com/dhh/you-can-t-get-faster-than-no-build-7a44131c
• https://world.hey.com/dhh/once-1-is-entirely-nobuild-for-the-front-end-ce56f6d7

[juliaogris]

This is on going work but it's been started: We are using import maps for the playground, and we have factored out: editor.js, and confetti.js

A next big step will happen when rendering docs as part of evy.dev. For that we will need an easily, flexibly embeddable evy editor (eventually) - so that samples are editable / playable.