Add Options to terminate temporary debug console on exit

[jborean93]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been requested.

Summary

I would like the temporary debug console to close and be removed from the terminal pane after a debug session is complete. It would make sense for the default to be set to not terminate to align with the current behaviour but there might be argument to have it terminate by default when attaching to another process through the computerName, processId, or customPipeName options as there is no local state that would be of use for the user post debugging.

Proposed Design

I assume this could be done in the DisconnectRequest handler to close the process and terminal pane in the VSCode editor.

[JustinGrote]

As discussed on Discord, I'd ideally like to define a leaveOpen or similar debug option, and that option is false by default with a launch and true by default with an attach, allowing for 4 combinations.

And what would be "killed" is the PSES instance starting the DAP runspace. If this was done in a separate process, that separate process would also be killed. If it's in the same process as PSES LSP, obviously leave that running as an exception.

IMHO ideal design as well we may want to investigate:

1. LSP has its main Runspace in the "main" process
2. DAP Server is always started as an additional runspace in the same "main" process
3. DAP "interacts" with a "remote" runspace in that process, whether that is actually remote or something like a named pipe. This would enable basically anything reachable via remoting and custom transports to be debuggable theoretically.

Only thing is that cleanup and cancellation might end up being difficult that would make sense for DAP to always be its own separate pwsh (or not!) process, that allows for immediate cancellation without coordination by simply killing the process.