Allow modules to provide rules

Summary of the new feature

as a user/developer I would like to have rules be defined as a part of a module.

As it stands now, the only possibility i can see right now to import "custom" rules is via CustomRulePath, however documentation and testing leads me to believe this only supports a known static or relative path.

Proposed technical implementation details (optional)

As a part of your documentation you talk about MEF, but this is possibly only for CustomRulePath? I can see as part of instance that you have ValidModPaths, but it seemes to only have data appended by methods in reference to GetValidCustomRulePaths()?

• checking all commands in psmodulepath that outputs Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.DiagnosticRecord?
  • Alternativly you could have the module require to have psdata.ExternalModuleDependencies defined to scriptanalyzer?
• alternativly you can add usingModules to settings so you dont need to re-check all modules in current runspace, but just the ones defined by the user

I want Scriptanalyzer to also check available rules from modules.

What is the latest version of PSScriptAnalyzer at the point of writing
1.24.0

Start by reviewing the documented CustomRulePath and MEF behavior, then inspect ValidModPaths and GetValidCustomRulePaths() to understand current custom-rule discovery. Clarify the intended module discovery or configuration approach and define how available module rules should be recognized as DiagnosticRecord implementations.