Add configuration option to issue a signal when the Stop button is clicked in debugger

Feature Request

My application terminates via SIGINT or SIGTERM where it can gracefully exit with a shutdown process. This cannot happen with the current debugger as the current stop button implementation immediately terminates (with a SIGKILL?).

I will borrow the proposed solution from another request:

{
  "configurations": [
    {
      "name": "MyApp Debug",
      "type": "cppdbg",
      "request": "launch",
      "program": "${cwd}/myapp",
      "args": ["-d"],
      "stop_action": "SIGKILL", // this would be a new enum-like config option, with values of "SIGKILL", "SIGINT", "SIGTERM", maybe others
    },
  ]
}

That is, to add an option in the launch.json to set the signal that is sent when pressing the stop button.

My current workaround is to use the pause button and then issue the -exec signal SIGTERM to the debugger which will send the signal. This is quite cumbersome when you're debugging and have to start and stop multiple times.

Start with the launch.json configuration handling and the debugger Stop-button entry point; the issue does not name repository files or tests. Compare the current stop behavior with the documented -exec signal SIGTERM workaround. Done means a configuration option lets users choose the signal sent when Stop is clicked, including the proposed SIGKILL, SIGINT, and SIGTERM values.