PowerShell
Use fuzzy matching for some error cases
Summary of the new feature / enhancement
One use case that was hit recently is someone was switching between using WindowsPowerShell and PowerShell 7 and the module with the DSC resource they were using was only installed for PowerShell 7, but they specified Windows PowerShell. In this specific case, it was not obvious to them why DSC reported that the module was not found.
Proposed technical implementation details (optional)
Although it might not help in this specific case, it might help generally when people are handcrafting configurations and making typos particularly where it's case-sensitive. So there may be places like resource type names, resource properties where we can apply a fuzzy match to tell the user "did you mean X?" instead of just reporting that "Y didn't match the schema" or "Y was unexpected".
