ci: build with deno v2

[mrstork]

Description

• Used Deno v2.2.4 consistently across all CI workflows.
  After merging, Deno v1.46.3 will have to be replaced by Deno v2.2.4 in local development environments
• Vendoring modules does not include type files by default, so those have been added to the vendor list
• We aren't using vendor: true in deno.json as it prevents relative imports in edge
• Moved deno.json into edge-runtime/ so that Deno v2 builds the vendor directory in that folder instead of the root
• The package size failure is happening because the report compares the code in main to the code in this pull request, but deno vendor (which is used in main) is deprecated in Deno v2, thus results in a build failure.