Small enhancements to temporary debugger console

I appreciate the temporary debugger console option (powershell.debugging.createTemporaryIntegratedConsole). But it suffers from some small usability issues.

(1.) It is configured in settings as a global option rather than per launch config when actually it configures launch config behaviour. This means if we need to turn it on and off (for example to avoid continual re-attach with C# debugger) it's not very convenient.

(2.) There is no ability to perform a second round of debugging in the temporary debugger console without re-creating the process which hampers further investigation of an issue.

I would like to suggest the temporary debugger console option become two launch config options:
(a.) "console selection": allows launching debug session using separate debugger console rather than normal integrated console (and in such case doesn't re-create debugger console if already present)
(b.) "force new console": re-creates console before starting debug session (could apply regardless of console selection)

These two options would allow much more flexibility with launch configs and allow having a stable process for C# debugger attachment when using the debugger console.

Start by tracing the powershell.debugging.createTemporaryIntegratedConsole setting and the launch configuration handling that controls the temporary debugger console. Compare the current behavior with the proposed console selection and force new console options, including repeated debugging and stable C# debugger attachment, then define tests for each behavior.