Support .js file extensions for TypeScript ESM on Node

[khalil-omer]

Relative import paths need explicit file extensions in EcmaScript imports when 
'--moduleResolution' is 'node16' or 'nodenext'. 
Did you mean '../inputTypeSchemas/NullableJsonValue.js'?ts(2835)

When useMultipleFiles is true, the imports between generated files throw errors if using modern module resolution in the tsconfig.

[lugrinder]

I adhere to this request, please add file extension on this situation.

[PS1TD]

Really need this. Without .js extention on prisma client path and also on between file imports if multiple files is turned on cannot use this generator in esm projects

[PS1TD]

Found a workaround for now.
Transpile using Babel with "babel-plugin-add-import-extension" plugin.
Also set module: "Bundler" in tsconfig

[anden-akkio]

This makes the project a non-starter for us

[askorupskyy]

big issue for my project, i will try to take this on

[Heartade]

I've implemented this on my fork, but the fork also contains a couple breaking changes (including full migration towards Zod v4) and I haven't been keeping my commits tidy.

Drafted #352 in case someone wants to take a look!