Fix property naming and settings catalog handling

[FabienTschanz]

Pull Request (PR) description

This PR fixes three issues with the settings catalog: One was a not handled case of a property name simplification, the second one in the same resource was an incorrectly generated property name, and the last issue in the second resource was a upper vs lower-case property name.

This Pull Request (PR) fixes the following issues

• Fixes IntuneAccountProtectionLocalAdministratorPasswordSolutionPolicy/IntuneSecurityBaselineMicrosoftEdge: Not deploying correctly #5378

[ricmestre]

I'm still trying to figure out what's going on with IntuneDeviceConfigurationCustomPolicyWindows10 and I'll test your diff once I'm finished with that one, but at least for IntuneAccountProtectionLocalAdministratorPasswordSolutionPolicy are you sure that PasswordAgeDays_AAD is the only property that needs the casing changed?

Additionally I remember that I already had to change the casing on that specific property a couple of times in my tests to cope with these issues, isn't there a better way to handle this?

[FabienTschanz]

The issue is that we use hashtables for the property lookups. Hashtables are case-sensitive regarding their properties, but I can try and check if the casing can be ignored. Unfortunately that will generate a bit of overhead.

Edit: Yes, I'm sure of it. That's because this is one of the two properties with the name PasswordAgeDays, and this one only differs from the other one in its definition id.

[ricmestre]

Both seem to be working with this diff 👍

I'll run all my unit/integration tests again just in case.

[NikCharlebois]

@ricmestre were your tests successful?

[ricmestre]

Unfortunately I found a couple of issues, of my own not DSC, so I had to fix them in the meantime.

I'm currently running the tests again right now, I'll let you know how it went in a couple of hours.