improve bundling, demo and hover rendering

[acao]

• finish the reorg @imolorhe started - consistent file names, move features to features directory
• switch to nodeResolution: bundler for esm, get rid of .js imports but still something newer than Node. keep nodeResolution: Node for cjs
• fix some issues with hover rendering, add hover rendering of $ref pointers! (see image)
• demo improvements - persist the edited values, use shema cache, remember the chosen schema, and change the headers based on the chosen schema (going to improve this further)
  

[changeset-bot]

⚠️ No Changeset found

Latest commit: b149588

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

❌ Deploy Preview for codemirror-json-schema failed.

Name	Link
🔨 Latest commit	b149588
🔍 Latest deploy log	https://app.netlify.com/sites/codemirror-json-schema/deploys/65da1b2749831b0008d67906

[imolorhe]

Are we sure changing the module resolution wouldn't reintroduce issues? I see that we are removing the ".je" suffix which was added when fixing a reported issue with resolving the module

[acao]

@imolorhe great point - I looked up the source to cm6-buildhelper and they also use moduleResolution: node so we should match theirs, yeah

[acao]

@imolorhe this means disabling top level await, which also means we must instantiate the shiki renderer with an async iife :/

[acao]

forgot changeset for this 😆