feature: Take deno.json into consideration when resolving dependencies for deno scripts.

[pixeleet]

If a deno.json(c) is present in the root of the project, we should take it into consideration so we can map dependencies there. Since the addition of deno add {npm|jsr}:scope/pacakge it's quite convenient to use deno.json import maps.

[ghost]

As documented, windmill currently supports a package.json to specify package versions:

• https://www.windmill.dev/docs/advanced/dependencies_in_typescript#lockfile-per-script-inferred-from-a-packagejson

So I'd recommend the same strategy to apply for Deno. Then we can manage dependency versions globally as well as map them.

For a more elaborate insight on the why, read this article from the official Deno team:

• https://deno.com/blog/http-imports