Lack of compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11.

Summary of the new feature

Add compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11, potentially other supported OS/PowerShell combinations as outlined by https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle

As a user, I would like to be able to leverage the PSUseCompatibleCommands check against profiles reflecting the current state of the OS and PowerShell, rather than only dated profiles reflecting unsupported OS and PowerShell versions. I am not proposing removal of any old profiles, just creation of new ones and relocation of unsupported ones to the optional directory.

Proposed technical implementation details (optional)

It would be nice if the process to generate these was added to the CI process, so that as Windows and PS Core versions move forward, new profiles are automatically generated.

What is the latest version of PSScriptAnalyzer at the point of writing

1.24.0

Start by reviewing the existing PSUseCompatibleCommands compatibility profiles and the PowerShell support lifecycle linked in the issue. Determine which current PowerShell Core, Windows 11, and Windows PowerShell combinations need profiles, and how unsupported profiles are organized in the optional directory. Done means current profiles are available without removing older ones, with CI generation investigated as part of the implementation.