Deno runtime support

[thescientist13]

Type of Change

Feature

Summary

Splitting of from #953 and based on some initial prototyping being conducted here, it seems like there should be a path towards basic Deno support for Greenwood.

What does that mean in pratice? Effectively instead of using npm and node, leverage the equivalents in Deno

$ deno install
$ deno task dev # maps to `greenwood dev`

Details

Some of the main considerations to account for as part of this work

1. Figure out why greenwood develop is showing a blank page
2. Seems like we'll need a standalone issue to prefix node_modules with npm: and NodeJS built-ins with node: - prefix NodeJS built-ins with node: #1324
3. 🚨 Deno won't be able to support custom loaders - Public API for compilers denoland/deno#1739
4. Validate Deno deploy support
5. Include a GitHub action to validate all test cases during Greenwood CI
6. Add documentation to the Greenwood website