Fix loading of built-in plugins when using an ESM or TypeScript config with the Standalone CLI

[thecrypticace]

In the case of a config that's not directly loadable by NodeJS — for example because it is TypeScript, ESM, or uses unsupported syntax, we invoke JITI to load the config file.

Normally there are no problems caused by this. However, in the standalone CLI we provide our plugins already built-in. This becomes a problem because JITI uses a version of require that we were not patching to load the built in plugins.

Making this work is a bit more complicated than it seems at first glance and relies on an internal implementation detail of JITI. However, it's probably one that's not subject to change too much (… famous last words — I know)

Basically we now:

• Patch require and require.resolve that's available natively to every module loaded by Node
• Patch createRequire to return patched require + resolve functions that work the same way
• Overload the JITI instance used so we can provide additional options that effectively instruct it to always use the "native" require to load the module rather than trying to find it on the filesystem

Fixes #12374

[thecrypticace]

@RobinMalfait any objections to my useCustomJiti thingy?

I can't override loadConfig directly I'm pretty sure because it's compiled as a non-configurable property of the module's exports.

[privatenumber]

If you're interested, tsx just released a tsx.require() and register/unregister functions if you want to load TypeScript/ESM files: https://tsx.is/node#only-commonjs-enhancement

Since tsx adoption is quite high, leveraging it if it's already available could be an option.