Test: debug process termination signal

[isidorn]

Refs: #54384

• macOS @aeschli
• Linux @roblourens

Complexity: 3

Authors: @weinand, @isidorn

In this release the "Debug: stop" command (either from the command palette or the debug toolbar) does no longer kill the debuggee forcefully but gives it a chance to terminate itself gracefully.

For Node.js debugging this means that the debuggee receives a SIGINT signal (which results in a termination if not intercepted).

If the debuggee fails to terminate, triggering the "Debug: stop" again will forcefully kill the debuggee (like VS Code did previously).

Verify for Node.js debugging that:

• Triggering a debug stop command can be intercepted by the debuggee by the approach shown below,
• Triggering a debug stop command for the second time forecfully kills the debugee,
• Termination signal is not sent for "attach" configurations,
• Extension host debugging works like before (you can start, reload, restart, quit with no problems).

a snippet for intercepting the SIGINT:

process.on('SIGINT', () => {
    console.log('Received SIGINT.');
    process.exit();
});

let i= 0;
setInterval(() => {
    console.log(`hello: ${i++}`);
}, 1000);