Fix #1247 - Maven build use node from PATH on mac os

[zulus]

Introduce NodeJSManager helpers to always produce ProcessBuilder with commands:

node_executable npm_location rest commands

these command is also used in NpmLaunchDelegate!

[vrubezhny]

@zulus I don't get how does it help to use embedded Node.js instead of a version that is found and used when npm (or NPM.CMD) is executed with

#!/usr/bin/env node

[zulus]

@zulus I don't get how does it help to use embedded Node.js instead of a version that is found and used when npm (or NPM.CMD) is executed with

#!/usr/bin/env node

Because rather than just run:
$: npm install something

Based on executable location search for cli.js (or npm-cli.js) and execute:

$ path_to_npm_builtin_or_from_property path_to_cli.js install something

[zulus]

Just check console log for tests (MacOS, Windows, Linux)

[vrubezhny]

Won't this path_to_cli.js still be executed with #!/usr/bin/env node?

Just check console log for tests (MacOS, Windows, Linux)

I had Node.js 20 configured for this purpose on MacOS GitHub build action :)

[zulus]

Won't this path_to_cli.js still be executed with #!/usr/bin/env node?

Just check console log for tests (MacOS, Windows, Linux)

I had Node.js 20 configured for this purpose on MacOS GitHub build action :)

No, `#!' is run structure for unix "*sh" only, for node (any js interpreter) is just a comment, in same way works "runnable" PHP/python/ruby scripts. On windows npm.cmd, doing nearly same as my path, search for node.exe, cmd.js and later just run command "node jsfile other params"

[vrubezhny]

On windows npm.cmd, doing nearly same as my path, search for node.exe, cmd.js and later just run command "node jsfile other params

So, npm is taken from your path (from the given cli.js path), while the node.js executable is still the system one?

[zulus]

After this path no both will be directly from embedder

[vrubezhny]

Looks good to me