PR Summary

This addresses Issue #2453
This PR allows Enter-PSHostProcess to work from within an SSH remote interactive session.

PR Context

Interactive session second hop support was added a while ago, but current behavior is to restrict a second hop to work only from a WinRM remote session. This is an unnecessary restriction and this PR allows both Enter-PSSession and Enter-PSHostProcess to work from within any interactive remote session.

Example:

PS> Enter-PSSession -HostName localhost
[localhost]: PS> Enter-PSHostProcess 8380
[localhost]: [Process:8380]: PS> $pid
8380
Exit-PSHostProcess
[localhost]: PS> Exit-PSSession
PS> 

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed: Need to document new second hop behavior for interactive remote sessions MicrosoftDocs/PowerShell-Docs#5468
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).