New Rule Suggestion: PSAvoidShorteningParameterNames

As long as we're trying to get people to stop using aliases and positional parameters and shortened command names, we should fix the parameters too.

Summary of the new feature

A new rule that complains when you write Get-Content -Pa file.txt -ov contents and offers suggestions with the full proper parameter name of each parameter: Get-Content -Path file.txt -OutVariable contents

It should complain about shortened parameters and parameter aliases, when you're passing them directly -- but shouldn't worry about splatting or pipeline properties, etc.

Bonus points if you make it a ConfigurableRule with a setting to ignore parameter names that match aliases (as opposed to just being shortened forms of parameters or parameter aliases).

Double bonus points if you make AvoidPositionalParameters also a ConfigurableRule so people can choose to fail even if only one positional parameter is passed.

No files or tests are named. Start by locating the existing AvoidPositionalParameters rule and the ConfigurableRule pattern in PSScriptAnalyzer, then trace how rules inspect command parameters. Done means the new rule handles shortened names and aliases while excluding splatting and pipeline properties; the optional configuration and AvoidPositionalParameters changes are separately supported if implemented.