Test: debug target launching in integrated terminal

[weinand]

Test for #10574:
complexity: 4

• Windows - @ramya-rao-a
• OS X - @sandy081
• Linux - @rebornix

In this milestone it is now possible to launch the node debug target in the 'integrated terminal' which helps when developing node.js-based command line applications that read from input and/or need to control the terminal they are running in.

Since there are now three options where to run a node program (debug console, integrated terminal, external terminal), we've deprecated the launch.json boolean attribute externalConsole and introduced a new attribute console which accepts the following values: internalConsole, integratedTerminal, externalTerminal.

Please verify:

• launching the debug target in the integrated terminal works. Make sure that passing arguments, environment variables, and 'cwd' work even if the values include spaces or quotes.
• the other two console options internalConsole and externalConsole continue to work.
• the new attribute console shows up in hover help and newly created launch.json uses it instead of the deprecated externalConsole.
• the old externalConsole options still works if no console option is specified.

Please note:
The problem that every debug session creates a new terminal is already tracked here: #10940