[Work Item] Improve power plan detection in HealthChecker

Describe the work
Today, HealthChecker is able to properly detect if one of the default high performance power plans is set on the OS:

Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance)
Power Scheme GUID: db310065-829b-4671-9647-2261c00e86ef  (High performance ConfigMgr)

However, if customers create a custom power plan, Windows generates a new GUID, which breaks our logic that we use in Get-PowerPlanSetting.ps1. This may result in false positives, because if the custom power plan is configured as we expect it to be, we are not able to properly detect the power settings (since we just check for the GUID and not for the settings of the power plan).

The same situation would happen in case that the default high performance power plan was adjusted and is no longer a "real" high performance power plan (because some of the new settings throttle system performance). We would show this configuration as good, since the GUID doesn't change in that case.