PSScriptAnalyzer: Remove PSAvoidUsingWriteHost from required rules

[dan-hughes]

Looking at the docs, it looks like if using PS5.0+ using Write-Host looks to be a non issue now as it wraps Write-Information.

Worse case is move it to flagged rules to allow it to be suppressed on a repo by repo basis.

[gaelcolas]

In terms of the language, yes I agree it's a non-issue.
But in terms of DSC Resource, I think it's still valid to some extent.

Since DSC is often run "by something out of process" (be it the LCM, the DSC.exe or something else), interactive host messages should be avoided (yes, what was a "MUST" becomes a "SHOULD", in principle).

Using Reasons or reflecting within the state might be a better approach.

[johlju]

I think if we could use different settings files on different parts of a module; a separate settings file for running tests on:

• Class-based resources / MOF-based resource
• Classes, Enums, Public, Private

For example having the ability for a repo to override the settings file if the repo provides on in a certain location.

The only negative thing is that for VS Code to use the same settings there can only be one settings file. So maybe DSC Resource HQRM tests should always use the settings file in .vscode folder if it exists (same as VS Code uses): https://github.com/dsccommunity/SqlServerDsc/blob/main/.vscode/analyzersettings.psd1
https://github.com/dsccommunity/SqlServerDsc/blob/755ad312e2817da020b4062477e111291374b56e/.vscode/settings.json#L16