The resolver doesn't know about Deno's global types

[RobertAKARobin]

In this issue typescript-eslint/typescript-eslint#5921 we tried using eslint-import-resolver-deno to support Eslint rules on a Deno project. But we ultimately gave up — imports from remote Deno modules were being typed as any, and we suspect that's because Eslint doesn't "know" about Deno's global types, e.g. Deno.errors, Deno.Addr, etc.

This isn't really a bug, just an FYI in case you're looking for additional features to add to this package.

Really great work with handling the import URLs! :)