[BUGFIX beta] Re-add support for moduleResolution=node10

[NullVoxPopuli]

VM PR: glimmerjs/glimmer-vm#1741

Text from that PR Description:

This feels crazy to add support for the node10 moduleResolution setting, but as pointed out in:
#20876

Some projects aren't up to date enough to use more modern moduleResolution settings -- and every TS dep needs to be compat with both in order to allow a consumer to migrate.

From the tsconfig docs

Default: Node10 if module is CommonJS; Node16 if module is Node16 or Node18; NodeNext if module is NodeNext; Bundler if module is Preserve; Classic otherwise.

No one should be using Node10 if they're writing ESM.

moduleResolution: node was renamed to moduleResolution: node10 with the release of TypeScript 5.0, which was released in March of 2023, which at the time, ember LTS was 4.8 with 4.12 being released on May 2023.

So it is within the TS Rolling support policy to be reasonable to have dropped support for moduleResolution: node10, and earlier TS versions.
(assuming config changes't aren't covered under semver-ts -- I opened this issue on semver-ts)

However, supporting node10 is easy, as this PR is one line change in each published package.json

[ef4]

@kategengler can we get a new beta that includes this?

[kategengler]

@ef4 Is it urgent or is the regularly schedule beta on Monday okay?

[ef4]

Regularly scheduled is fine, just wanted to make sure it gets into some beta. Thanks.