Additional settings file for developement #2184

Summary of the new feature

There is currently one PSScriptAnalyzerSettings.psd1 file shipped with the PSScriptAnalyzer but there are at least two use cases with a different requirement:

• Design-time
  During this phase (often done is VSCode or Visual Studio), any cutting-edge alert for a potential PowerShell pitfall is welcome.

• Continuous Integration
  During this phase (e.g. in a CI/CD street), any change is supposed to passed the given tests.

Apparently, there is a (undocumented?) convention that our convention is to ship it opt-in via ConfigurableRule with Enable = false but that convention only satisfies the builder phase.

Proposed technical implementation details (optional)

Ship the PSScriptAnalyzer with an additional settings file that is focused on the development phase.
The "development" settings file might than be used as a default by e.g. VSCode (powershell.scriptAnalysis.settingsPath).

Caveats

• The settings file under VSCode "This setting may not work as expected currently!", see: powershell.scriptAnalysis.settingsPath (Description): Warning Message Should Provide A Workaround vscode-powershell#4653
• default settings for PSScriptAnalyzer are different to the CLI vscode-powershell#5385? "Users keep getting bitten by the extension's effective defaults differing from Invoke-ScriptAnalyzer's defaults", I believe this isn't a feature but a bug, see: VSCode doesn't show CommandElementAst problems vscode-powershell#5474

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

1.25.0