feature(runtimes): #1322 deno runtime support

[thescientist13]

Related Issue

resolves #1322

Documentation

1. document Deno runtime support + Deno Deploy www.greenwoodjs.dev#295

Summary of Changes

1. Add runtime support for Deno in the CLI
2. Add runtime support for Deno for Lit Renderer plugin
3. Add deno as a package manager option for the init package

Upstreams

1. Deno support in gallinago - add Deno support thescientist13/gallinago#79
2. had to sort pages / plugins (should make as its own issue) - make page and internal plugins loading order deterministic #1797
3. had to have greenwood serve use the right API worker (should make as its own issue) - fix(cli): #1694 serve lifecycle not honoring renderer plugins api route handlers #1799
4. concurrency configuration enable throttling of max number of pages that can be prerendered at once #720

TODO

1. GitHub Actions for Deno
2. Support deno install in init package
3. avoid 0 minimum dependency age flag in Deno install via Init CLI
4. add windows test cases
   • deno init is failing
   • GraphQL test failure
5. getting intermittent panics from Deno 😬
   • https://github.com/ProjectEvergreen/greenwood/actions/runs/34709369391/job/103595168833
   • https://github.com/ProjectEvergreen/greenwood/actions/runs/34724786684/job/103636913066
6. how to handle @rollup/wasm-node@4.62.3?
7. what about using Deno APIs, like reading a file?
8. clean up comments
9. Contributing
10. Final Documentation tracking - Deno upstream tracking items #1810
    • notes for website docs
    • capture TODOs / Deno-isms as a discussion
11. Include Deno CI checks (post merge)

Questions

1. Should we use a deno.lock file? (would also need postinstall support) - will just rely on monorepo package manager for now
2. do we need to worry about #!/usr/bin/env node? - No, Deno will run anything run with deno task using the deno binary - https://docs.deno.com/runtime/reference/cli/task/#node-and-npx-binary-support