Migrate to JSR.io

[MasterKale]

A PR to track work required to support hosting the project on jsr.io.

Related to #571.

TODO

• Figure out UMD hosting if everything was on JSR.io
  • Some combo of Deno + Rollup?
• Figure out some kind of versioning script I can run to see what packages got updates between "now" and the latest version tag
  • This would be a hand-rolled, minimal replacement for lerna version
• Figure out what deploying new releases would look like
  • Right now this would involve manually bumping versions in deno.jsonc files and then publishing
• Decide if JSR hosting really can replace NPM and deno.land/x hosting, just replace deno.land/x, or maybe become a third option to maintain (😮‍💨)?

Updates

11/9: I've got v11 of everything hosted on JSR as "11.0.0-alpha2" releases while I'm still testing things out:

[MasterKale]

Quick check-in, I managed to get @simplewebauthn/types@11.0.0-alpha1 published:

https://jsr.io/@simplewebauthn/types@11.0.0-alpha1

This includes functional DOM types extraction just as I had before, except pulling from Deno's cache.

[MasterKale]

Checking in: all three packages have been been published to JSR as v11.0.0-alpha2 🎉

https://jsr.io/@simplewebauthn

All browser and server tests have been migrated to use Deno testing, and DNT has been removed from server.

Rollup is not being used right now to bundle browser. The UMD build is also not available with what's on JSR.io afaict. I still want to be able to offer it if I decide to migrate package hosting to JSR.io, though. I'm going to investigate this now that I feel reasonably certain that everything can exist as a Deno codebase.

[MasterKale]

I requested some assistance testing all this out over here:

#542 (comment)