PR Summary

Fix #2692

Add -StrictMode to Invoke-Command to allow specifying strict mode when invoking command locally.
The -StrictMode parameter sets the provided version to the process. Once the process completes, the StrictMode version is set back to what it was before the Invoke-Command.

It does not support asynchronous jobs on remote machines. Applying a StrictMode version for a remote session is not a trivial change. The StrictMode version would have to be communicated to the target so that it can be applied to the Runspace in the remote session.

In addition to the implementation, an Invoke-Command test file was created with -StrictMode tests.

PR Context

This pull request was opened in response to the "Invoke-Command should support -StrictMode #2692" issue. Now, Invoke-Command supports a -StrictMode parameter.
StrictMode establishes and enforces coding rules in expressions, scripts, and script blocks. This can be useful for running scripts with basic best-practice coding rules. Even though this is not an implementation for async jobs, there are still many useful applications for StrictMode in local processes.

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: Add Documentation for Invoke-Command StrictModeVersion Parameter MicrosoftDocs/PowerShell-Docs#8459
• 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 opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: