Add ability to determine when script uses language features and/or cmdlets not available in the specified minimum version of PowerShell

This is increasingly becoming an issue as PowerShell gets new language features and cmdlets. And cmdlets get new parameters, etc. I could have a #requires -version 3.0 in my script but I'm developing on PowerShell 5.0. It is real easy to slip up and use a lang feature ("using namespace System.Diagnostics") or a cmdlet (New-TemporaryFile) or a new cmdlet parameter (PassThru added to Enable-JobTrigger in v4). It would be great if ScriptAnalyzer saw a #requires -Version X.0 and warned (or errored) when I used a feature not available on X.0. Likewise, I would like to have a parameter to ScriptAnalyzer where I could tell it the minimum version I want to target (perhaps I have several scripts written at different times that have varying levels of #requires -Version).

For bonus points, if someone specified neither the command line parameter (MinimumPowerShellVersion) or had any #requires or min version in their PSD1 file, it would be nice if ScriptAnalyzer told me that - "Scripts require at least version 4 due use of -PassThru parameter on Enable-JobTrigger and use of Get-FileHash cmdlet).

Where things get a bit more tricky is setting a minimum Windows OS version. But the need is there since I have a whole bunch of cmdlets available to me on Windows 8.1 that I know are not available on Windows 7.

まず ScriptAnalyzer のエントリポイントと、現在 #requires 宣言、cmdlet の使用、言語機能、パラメーターをどのように処理しているかを確認します。最小バージョンの指定元であるコマンドライン入力、#requires、PSD1 メタデータを比較し、Windows バージョンの場合を含め、サポートされていない機能を警告でどのように識別するかを定義します。完了条件は、対象範囲と互換性ルールが、対象を絞ったアナライザーのテストを追加できる程度に十分明確に仕様化されていることです。