feat: enable explicit resource management for JavaScript

[bartlomieju]

This commit enabled [explicit resource management]
(https://github.com/tc39/proposal-explicit-resource-management)
proposal for JavaScript code.

This is done by upgrading deno_ast to a version that no longer
transpiles TS files with using keyword, and instead enables
a V8 flag that provides native support.

Closes #20821

[bartlomieju]

Need to land denoland/deno_ast#290 first and add a test that uses using keyword in a JS file.

[dsherret]

LGTM!

[lucacasonato]

We can't land this - V8 does not call the dispose method with the correct receiver when await using falls back to [Symbol.dispose]: (async () => { await using foo = { [Symbol.dispose]() { console.log(this, "asd") }, foo: "bar" }})(). I file a V8 bug and ask them to hold this (ie not ship in Chrome 134.

[0f-0b]

Just tested this branch and found another bug where a top-level await using crashes the process.

console.log("before await using");
await using _ = {
  [Symbol.dispose]() {
    console.log("dispose");
  },
};
console.log("after await using");

[lucacasonato]

@0f-0b Thanks, filed https://issues.chromium.org/issues/396661138.