UseCorrectCasing Publishes Warnings instead of Informational in VS Code

[bmkaiser]

Before submitting a bug report:

• Make sure you are able to repro it on the latest released version
• Perform a quick search for existing issues to check if this bug has already been reported

Steps to reproduce

Using PowerShell Extension v2024.2.2

get-process

Expected behavior

Based on the documentation for UseCorrectCasing, the rule severity is only supposed to be Informational.

Actual behavior

Problems are being reported as Warnings instead.

If an unexpected error was thrown then please report the full error details using e.g. $error[0] | Select-Object *

Environment data

> $PSVersionTable  

Name                           Value
----                           -----
PSVersion                      7.4.5
PSEdition                      Core
GitCommitId                    7.4.5
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

> (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }
1.23.0
1.22.0
1.21.0
1.22.0

[bergmeister]

@andyleejordan Probably one to consider before the next release, I opened a small PR for it
I think the original intent was warning because it's a formatting rules that people usually wouldn't lint on but kind of agree that Info level is probably more appropriate