Check for platform-dependent path usage

As suggested by @SteveL-MSFT.

A rule that checks/corrects filesystem path usage that doesn't translate across between Windows and UNIX-like OSes could ease migration to PowerShell Core.

User story

As a PowerShell user, I want a rule to tell me when a path I've used
will break my script on another platform, so that I can write
cross-platform scripts more easily (e.g. for Azure scenarios).

Proposed technical implementation

Check all *-*Item and *-Path cmdlets (and their aliases) for direct string/bareword arguments to check for platform specific usages (like C:), or even encourage usage of Join-Path or [System.IO.Path]::Combine() instead of / and \.

Of course this check isn't universally feasible, but this is another case where some constant folding would come in handy for PowerShell analysis (something PSES could also use).

Latest current version of PSSA

1.17.1

此 issue 未指定檔案、測試或現有的規則進入點。先檢視 PSScriptAnalyzer 如何實作規則，以及它如何識別 *-Item 和 *-Path cmdlet 與別名。在實作之前，先定義支援的平台特定模式與常數折疊範圍；完成的標準是該規則能偵測約定的案例，並在支援的情況下透過測試加以修正。