Support modern ESM imports in Node for Max

Hi all, I'm working on a project involving Node for Max and struggling to get a basic non-trivial patch running.

Correct me if I'm wrong, but even with a custom @node_bin_path Node binary specified it seems like the node.script node process manager object in Max is hardcoded to import user scripts using the outdated CommonJS `require('xyz')` syntax.

In `/Applications/Max.app/Contents/Resources/C74/packages/Node for Max/source/lib/nsRunner.js`:

// Kick off things and load user script
require(process.env.SCRIPT_PATH);
loadedSuccessfully = true;

The README states that Node v16.6.0 is used internally. In Node.js v12.17.0 and above it's possible to use dynamic imports. A compromise could be:

// if package.json nearest to the user script has type: 'module'
// or the script file ends with .mjs
import(process.env.SCRIPT_PATH).then(() => {
loadedSuccessfully = true;
})
or something less hacky.

These days, a number of package dependencies are being published in ESM-only formats. The broader implication is that it's not always feasible to convert an entire script to CommonJS. A modern Node project often comes with additional complexity, especially if there's Typescript transpilation or bundling involved. Often there are packages involved with add-on Node-API binaries (`.node`) that cannot be bundled and need to be marked as runtime externals (in my current case, one that's adding WebRTC support for Node).

Is there a currently preferred workaround or consideration for this? It seems like I would have to resort to some kind of a Max for Node proxy to exchange messages with a locally running, completely separate node process.