fix: esm customizer for typegate deno ext

[Yohe-Am]

Enables v8 snapshots integration for meta typegate subcommand and the standalone typegate. Also bumps deno to 1.41.0.

Motivation and context

Fixes #591

Migration notes

No changes required

Checklist

• The change come with new or modified tests
• Hard-to-understand functions have explanatory comments
• End-user documentation is updated to reflect the change

[linear]

MET-400 `meta typegate` doesn't work

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.14%. Comparing base (977a0e1) to head (21f6418).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #606   +/-   ##
=======================================
  Coverage   74.14%   74.14%           
=======================================
  Files         111      111           
  Lines       12425    12425           
  Branches     1313     1313           
=======================================
  Hits         9213     9213           
  Misses       3192     3192           
  Partials       20       20           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Yohe-Am]

Note: I also run into the same issues I'd faced with the snapshot based xtask in the customizer approach. (it wasn't related to snapshotting as it turns out. The snapshot setup did obscure it) but I did manage to fix it. I.e., I could probably go back to the snapshot paths at this point. I've decided against it though on the basis of compilation times.

The 2000 packages quote from last time turned out to be due to duplicate builds necessitated by build scripts (or some misuse on my part but I can't figure out where). 2000 packages not only takes way more time but adds way too much bloated artifacts which are even more painful at this point. It also seems to have made the cargo change detection more brittle, unnecessarily re-building packages leading to more artifacts.

We'll probably want to enable snapshots at some point but I think it might be better to keep it simple until our dependency tree has stabilized.