Build: Migrate create-plugin to ESM

[jackw]

What this PR does / why we need it:
This PR updates the create-plugin package to build only as an es module. The following changes have been made with reasoning on approaches:

• Updates Typescript config to output ESM. These changes are in line with tsconfig/bases/node20 suggested config. Having found these configs I'm wondering if we should update the entire repo to use them over writing our own.
• Updates all import paths inline with Typescripts requirements by adding .js extension to imports. Note that auto barrel file resolution (from './commands/' resolved to from './commands/index.js') no longer work with ESM. You have to reference a file. VsCode autocompletion seems to work out the box. I attempted to use a bundler ESbuild to prevent the need to change all these imports but hit a wall.
• Update all imports to use import over require. I'm not sure why utils.console.ts used require but changing them led to complications with TS types and needing to patch the marked-terminal package and set overrides for marked nested dependency.
• Replaces Jest with Vitest. Turns out Jest support for ESM is quite poor. Mocking in particular is complicated due to esm static import analysis and needing to use unstable_mockModule which I didn't particularly like the sound of. Vitest migration was quite painless, only the mocks needed some attention.
• Updates some dependencies to their ESM compatible versions. Other dependency updates will be done in future PRs.

Which issue(s) this PR fixes:

Related #654

Special notes for your reviewer:

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install @grafana/create-plugin@3.0.0-canary.658.52bb056.0
# or 
yarn add @grafana/create-plugin@3.0.0-canary.658.52bb056.0

[github-actions]

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged and will trigger a new major release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.

[mckn]

LGTM! Interesting since I tried to do the same thing with Levitate and manage to get everything working except the jest tests. But then the solution might be to migrate over to vitest.

[jackw]

But then the solution might be to migrate over to vitest.

Probably will make life much easier. Admittedly this is a small project but the Vitest migration was surprisingly straightforward. It was only mocks that needed any attention. Jest and ESM just don't very work well together. 😞

[grafana-plugins-platform-bot]

🚀 PR was released in @grafana/create-plugin@3.0.0 🚀