launch.json externalConsole=true in Remote-SSH contexts

[therealkenc]

When launching a debugger (in my case, vscode-cpptools) using a Remote-SSH session workspace with "externalConsole=true" set in launch.json, the external console (in my case gnome-terminal aka x-terminal-emulator) is launched on the remote side. The reason for this is well undersood; and indeed fair enough to call "by design". No problem there. But it isn't the behavior one will want in most dev scenarios.

Ask would be to launch a local x-terminal-emulator with a ssh session to the remote side; which is what in spirit happens with "externalConsole=false".

Motivation behind this is that in some client-server development scenarios you've got the service side dumping scads of caveman logging, and the (otherwise all-around awesome) internal terminal isn't ideal. You want your terminal output over in another window resized screen height. If the internal terminal could be peeled off à la vscode#10121 it probably wouldn't matter (and maybe would obsolete gnome-terminal altogether, laugh). But while that is not possible, externConsole=true is still useful.

[Awesomeness on the new feature BTW. You've made a lot of WSL developers very happy. 💯]

[therealkenc]

Ref related #267, Microsoft/vscode#67296 and Microsoft/vscode-cpptools#2998.

[VSCodeTriageBot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!