PR Summary

This PR removes the apartment thread state check when invoking a script on a PowerShell object for non-Windows platforms.

PR Context

I found this while testing SSH remoting on non-Windows platforms. Entering into an interactive session on an SSH remote connection between PS6 and PS7 results in an error. The error is due to the apartment thread state check, which should not apply to UNIX platforms. This is a regression.

The fix is to simply remove the check since it is not needed for UNIX platforms.

# PS 6 on Ubuntu platform making a remote connection to PS 7 on Ubuntu platform.
PS > $session = New-PSSession -Host UbuntuPS7
PS > Enter-PSSession $session
Enter-PSSession : When the runspace is set to use the current thread, the apartment state in the invocation settings must match that of the current thread.
At line:1 char:1
+ Enter-PSSession -Session $s
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Enter-PSSession], InvalidOperationException
+ FullyQualifiedErrorId : RemotePSInvocationStateInfoReason

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:
• 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).