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 及别名。在实现之前，先定义受支持的平台特定模式和常量折叠范围；完成的标准是该规则能够检测约定的案例，并在支持的情况下通过测试进行修正。