Actively warn user when PSIC is not active terminal during execution of PowerShell: Run Selection

[cruscio]

Prerequisites

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

Summary

If executing PowerShell: Run Selection when the active terminal is not a PowerShell Integrated Console (e.g. by a user switching between bash and pwsh tabs, on a Linux remote SSH session), it would be ideal to warn the user, instead of the current behavior to run the selected code in the active terminal regardless. This would prevent unintentionally, and possibly harmfully, executing commands in an unintended context.

The current behavior is to silently log a message and execute in the current terminal.

Proposed Design

The logic already exists to detect this scenario and log it. There would need to be a modified action after detection.

Couple proposals to be implemented by either a new configuration setting or by hard coding:

• Modify the behavior to prompt/warn/cancel, instead of just logging a message, when the active terminal isn't a PSIC.
• Modify the behavior to change the active terminal to a PowerShell Interactive Console before running the selection.

[andyleejordan]

Hey, I love this idea. We would take a PR that does the first proposal, but slightly modified:

If the current selected terminal is not the integrated terminal, prompt the user: explain what's going on, allow the user to cancel, proceed, or proceed and ignore going forward (this would be accompanied by a new extension setting that would default to false, but if true would not prompt).

The reason for allowing the existing behavior is that we have many users who want to execute the current selection in a pwsh terminal that is not the integrated terminal. Sadly this is because the integrated terminal is not (currently) as good as the normal terminal, but while it's improving this feature is a viable work-around.