Ability to bind concerned PowerShell version to a rule

It might be helpful that in the case a rule only applies to a specific (minimum) PowerShell versions as for e.g.:

• AvoidUsingWMICmdlet

And new request/issues:

• UseCompatibleStrings
• UseCompatibleSyntax
• AvoidNewObjectCmdlet

to have the possibility to add that (minimum) PowerShell version (e.g. MininumPowerShellVersion) to that rule.

Meaning e.g. the AvoidUsingWMICmdlet rule might have MininumPowerShellVersion set to 3.0
This would add the possibility for two additional features:

• Suppressing the specific rule by using the #Requires -Version x.x statement.
  E.g.:
  • adding #Requires -Version 2.0 would suppress the AvoidUsingWMICmdlet rule
  • adding #Requires -Version 7.0 would allow the use of `e (suppress the proposed UseCompatibleStrings rule)
• A general UseRequiresStatement rule when a rule with a minimal version applies and the #Requires -Version x.x is not set (or set incorrectly)
  E.g. if any of the rules applies, it generate a warning that the #Requires -Version x.x statement should be set.

Start by reading the AvoidUsingWMICmdlet rule documentation and the linked UseCompatibleStrings, UseCompatibleSyntax, and AvoidNewObjectCmdlet issues. Then trace how rules are represented and how #Requires -Version is handled. Done means the proposed minimum-version behavior, suppression, and UseRequiresStatement behavior have a defined implementation scope.