Add WinCompat deny list support using a setting in powershell.config.json

[anmenaga]

PR Summary

Some Windows PowerShell modules don't work well with de/serialized objects, so they can not be used with WinCompat.
This PR adds support for an optional WindowsPowerShellCompatibilityModuleDenyList setting (a string array) in powershell.config.json so that a user can prevent specified modules from being loaded using WinCompat.
If WinCompat feature is enabled and it tries to load a module mentioned in the DenyList, then an error is generated.
Module name comparison is case-insensitive.
By default, in PowerShell packages for Windows OS, this setting will contain PSScheduledJob,BestPractices and UpdateServices modules (this list most likely will be extended in future).

Fix #11687

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 docs about WinCompat DenyList MicrosoftDocs/PowerShell-Docs#5373
• 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).

[TravisEz13]

Is this needed for GA?

[TravisEz13]

@PoshChan Please remind me in 1 day

[anmenaga]

Codacy issue Make 'IsModuleInDenyList' a static method is wrong as it doesn't detect a call to non-static WriteError.

[TravisEz13]

@PaulHigin Can you update your review?

[TravisEz13]

Please resolve conflicts

[PoshChan]

@TravisEz13, this is the reminder you requested 1 day ago

[doctordns]

My earlier comment may have gotten buried - the WSUS module should be added to the WInCompat deny list.

[SteveL-MSFT]

Pending adding UpdateServices module to the list

[TravisEz13]

@SteveL-MSFT Please update your review?

[TravisEz13]

@PoshChan Please remind me in 1 hour

[SteveL-MSFT]

One NIT

[PoshChan]

@TravisEz13, this is the reminder you requested 1 hour ago

[TravisEz13]

@PoshChan Please remind me in 1 hour

[PoshChan]

@TravisEz13, this is the reminder you requested 1 hour ago

[ghost]

🎉v7.0.0-rc.3 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes