JS: Remove timeout for node --version check

[asgerf]

Attempts to fix https://github.com/github/codeql-javascript-team/issues/120 by disabling the timeout for the call to
node --version.

I was able to verify that the timeout can be triggered if the parent process (Java) is suspended during the interval where node is booting up. In a cloud computing environment, my guess is that this suspension happens when the entire VM is paused for some reason, and that the initial node call can be slow enough for the pause to occur during that time (e.g. some lazy initialization might happen).

The believe the robust solution would be to wrap node --version in a retry loop, but I instead decided to just remove the timeout. The timeout seems unnecessary since we afterwards start a node process without a timeout anyway.

[esbena]

We probably cant fix the following scenario, but what if node --version hangs because it isn't Node.js?
I remember seeing some rants about python opening up the Windows store if python wasn't installed...

[asgerf]

but what if node --version hangs because it isn't Node.js?

Well the retry loop would fix that, I think. I have the retry solution on a branch, so we can switch to that if you think it's better.

[esbena]

Well the retry loop would fix that,

Right. Lets try with the retry loop and timeout then.

I think support will be happy to not have to debug my scenario one day.