Set createTempIntCon when creating launch config for Pester test

[rkeithhill]

Fixes #1208

[daviwil]

Should the setting only be used when runInDebugger is true? I could go either way

[rkeithhill]

I think there is benefit in being able to run tests in a fresh session. Yeah, the [DGB] in the terminal name is bit of a misnomer in this case.

[daviwil]

Maybe if "runInDebugger" is false we can use a different title? That was short-sighted on my part

[rkeithhill]

Maybe [TMP] PowerShell Integrated Console ??

[daviwil]

Or [TEMP] just to be extra clear, but anything works

[rkeithhill]

I wish the VSCode folks would make this dropdown a tad wider:

What do you think?

[TylerLeonhardt]

LGTM with the same comment David has :)

[rkeithhill]

Which specific comment?

Right now, the behavior is that whether you are running Pester tests or debugging, if powershell.debugging.createTemporaryIntegratedConsole is set to true, either of these operations happen in the terminal window [TEMP] PowerShell Integrated Console. That terminal window sticks around until the next Pester test run or debug session at which time the existing PowerShell process is closed and recreated, attached to a new VSCode terminal window with the exact same name. [TEMP] PowerShell Integrated Console is effectively the one and only terminal window for "powershell.debugging.createTemporaryIntegratedConsole": true even though the associated PowerShell process changes with each run. I think that is what we want but if not, let me know.

[TylerLeonhardt]

Oh sorry, the comment on changing dbg to temp

[rkeithhill]

Thanks. Just pushed that change so I'll go ahead and merge this.