Enable enforcing consistent casing

Summary of the new feature

PowerShell code used in official examples and VS Code code generation seems to follow some basic casing conventions:

• PascalCase for
  • cmdlets
  • parameters
  • constants
• lowercase for
  • operators
  • statements (if, foreach, etc)
• camelCase for
  • local variables
• casing of module names and .NET types, enum values, etc consistent with their original case-sensitive casing

I would like to optionally enforce these casing conventions with PSScriptAnalyzer.

Proposed technical implementation details (optional)

I would like to enable rules in my PSScriptAnalyzerSettings.psd1 that enforce the casing rules above and autofix casing issues.

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

首先查看 issue 中提出的大小写约定，以及 PSScriptAnalyzer 设置如何启用规则。完成的内容应包括对所列大小写类别的可选强制执行和 autofix 支持，并定义对保持原始大小写的模块名称以及已定义 .NET 类型的行为。