Migrate to Deno

[stefnotch]

After having tried out the mini-parse migration, I thought of a few more tricks to make the migration easier. This is my WIP attempt to migrate everything.

Tasks to do:

• Build CLI and packager with https://github.com/denoland/dnt
• Build linker library with vite and publish that to npm? Unless dnt also transforms packages into a browser-compatible format?
• Fix LinkPackage.test.ts. (moved to packager)

Mostly mechanical edits I did

• Global replacing
  • .js" to .ts"
  • "mini-parse to "@wesl/mini-parse
  • ctx.task.name to ctx.name
  • test.skip to test.ignore
• removed berry-pretty
• Deno's testing utils don't support toMatchSnapshot. There is an async assertSnapshot function in @std/testing/snapshot instead. So I pulled out ast-grep to mostly mechanically do the edits sg --pattern 'expect($MATCH1).toMatchInlineSnapshot($MATCH2)' --rewrite 'await assertSnapshot(ctx, $MATCH1)' --lang ts --interactive and sg --pattern 'expect($MATCH1).toMatchSnapshot()' --rewrite 'await assertSnapshot(ctx, $MATCH1)' --lang ts --interactive

[stefnotch]

I removed LinkGlob.test.ts, since import.meta.glob is a vite-specific API. I wasn't sure what to do instead.

[stefnotch]

I replaced vite with the Deno testing facilities, mostly to reduce our dependencies.
If vitest does have some nice advantages, we should switch back to it.

[stefnotch]

I could simply import most dependencies from npm, but Deno usually has a nicer built-in alternative. So I figured I'd properly do the migration.

Yargs is a pretty good dependency though. The only alternative worth considering that I could find is https://cliffy.io/ .

[stefnotch]

It's all deno! 🦕

I guess that unified tooling aspect is reasonably nice. Hopefully the Node.js ecosystem will catch up and also get more unified tooling.