Test: Align functionality of node-debugger and chrome debugger

[chrmarti]

Test for microsoft/vscode-node-debug2#7

[roblourens]

Complexity: 4

If you set "type": "node2" in a launch config, you'll be using the new debug adapter, boom.

See notes in the release notes for an overview, especially the note about Windows support.

See this bug for an overview of what's implemented.

Most existing issues are filed in vscode-chrome-debug-core, node-specific ones are in vscode-node-debug2.

• - OSX @jrieken
• - Windows @mousetraps
• - Linux @kieferrm

There are a million scenarios we need to support, so the most valuable thing you can do is grab any random Node project that you might have debugged with VS Code in the past, change "type" to "node2", and see what happens. If anything happens that isn't the same as "node", is it obvious to figure out what's wrong?

More specific things to try, don't need to do every single one:

• Try some things that are checked off at Node CDP Debug tasks vscode-node-debug2#7
• Ensure it kills the process when terminating a launch config, but not an attach
• Set breakpoints before launching, and ensure they bind
  • In the main script, and in scripts that are loaded later
• Look in the variables pane at different types and compare it to what you'd expect
• Test very large arrays and other stress cases
  • It might get slow but it shouldn't crash
• Test with and without sourcemaps
• Attach config with a running process (start with --inspect=9229)