Do not open TTY (-it flags) unless needed

[sfertman]

You never know how external services may use node executable.
This is actually a problem if I'm using VSCode to debug a node application.
This one is a little bit more tricky to figure out.

• One option is to never open tty by default and have users pass --tty option if the want to run a repl.
• Another option is to do some basic parsing of node arguments and figure out if I need tty from that; but this could be complicated because cli is different between node versions.
• Another option is just to setup remote debugging in VS Code

[sfertman]

Option 2 above looks like something doable:
Node 6:

Usage: node [options] [ -e script | script.js ] [arguments] 
       node debug script.js [arguments] 

Node 8:

Usage: node [options] [ -e script | script.js | - ] [arguments]
       node inspect script.js [arguments]

Node 10:

Usage: node [options] [ -e script | script.js | - ] [arguments]
       node inspect script.js [arguments]

Node 12:

Usage: node [options] [ script.js ] [arguments]
       node inspect [options] [ script.js | host:port ] [arguments]

Node 14:

Usage: node [options] [ script.js ] [arguments]
       node inspect [options] [ script.js | host:port ] [arguments]

[sfertman]

To see the NODE_OPTIONS env that VScode starts debugger with, use "console": "integratedTerminal" option