Deno v2 And Imports

[jbolda]

Motivation

Deno v2 has arrived. Updating the bits to support using it. I ran a deno fmt as well to handle any formatting changes coming along in v2.

Additionally, I made the swap to use imports in deno.json. This is more newly supported, but provides a few benefits over dep.ts. Do note, any local / dev dependencies (see scripts or testing) still use a direct import out of convenience and less need for central control. The tests still use test.ts however to handle all deps including the additional helper functions.

It means that all of our imports can be listed in a central place much the same, but at the actual import location, we are able to specify the dependency from which it originates. This makes it clear when we are using a dependency directly as opposed to an extend version.

import { type Operation } from 'effection'

The dnt script is able to use these just the same, and it allows us to remove the mapping for most values. It more centrally handles the versions. The one caveat, if we want to use a deno based import still, we specify it as such in the deno.json imports and then provide a mapping when using dnt.

[neurosnap]

Thanks for spearheading, looks good to me!