Test: EH debugging

[isidorn]

• windows @sandy081
• macOS @aeschli
• linux @joaomoreno

Complexity: 3
Refs: #55955, #48377

We have refactored EH debugging to address issues like #55955. Open the hello-world extension (yo generator) in VS Code and verify:

• You can debug the extension by running it and hitting a breakpoint,
• Reloading the debuggee vscode window properly reconnects the debug session,
• You can restart the debuggee from the first window via debug toolbar - results in the reload of the second window. Verify breakpoints after this still get hit,
• Closing the debuggee vscode windows stops the debug session (toolbar is hidden),
• You can stop the debug session by clicking the red square in toolbar from the first window which will result in the second window closing,
• replace the body of the "extension.sayHello" command with code that invokes a command that has a EH reload as a side effect, e.g. this:

        vscode.commands.executeCommand('_workbench.enterWorkspace', vscode.Uri.file('/Users/johndoe/foo/bar.code-workspace')).then(_ => {
            console.log("ok");
        }, e => {
            console.log("error: " + e);
        });
  

  and verify that EH debugging is not blocked (as was seen in the original issue Broken EH debugging on Windows after window reloads  #55916).

After reloading/restarting the EH please make sure that the debugger connects properly to the new EH process by either

• waiting at least 10 seconds (because that's the timeout after that VS Code shows an error about the EH not running properly), or
• using any other proof that it runs (e.g. the git extension updates a badge with the number of changed resources)