Fix handling of DeviceCompliancePolicyScript property

[FabienTschanz]

Pull Request (PR) description

This PR fixes the handling of the DeviceCompliancePolicyScript property in the IntuneDeviceCompliancePolicyWindows10 resource. Previously, if this property was set, it would export a non-parseable string similar to System.Collections.Generic.Dictionary2[System.String,System.Object];`. This PR fixes this issue by exporting a CIM instance with the details of the property.

This Pull Request (PR) fixes the following issues

• Fixes BUG: IntuneDeviceCompliancePolicyWindows10: System.Collections.Generic.Dictionary #5510

Task list

• Added an entry to the change log under the Unreleased section of the file CHANGELOG.md.
  Entry should say what was changed and how that affects users (if applicable), and
  reference the issue being resolved (if applicable).
• Resource parameter descriptions added/updated in the schema.mof.
• Resource documentation added/updated in README.md.
• Resource settings.json file contains all required permissions.
• Examples appropriately added/updated.
• Unit tests added/updated.
• New/changed code adheres to DSC Community Style Guidelines.

[NikCharlebois]

That would be considered a breaking change. What is the current behavior? Is this resource even working today?

[FabienTschanz]

@NikCharlebois Currently, if you were to export this resource, it would end up with a broken export like the following:

IntuneDeviceCompliancePolicyWindows10 "IntuneDeviceCompliancePolicyWindows10-IntuneDeviceCompliancePolicyWindows10_1"
        {
            ...
            Description                                 = "";
            DeviceCompliancePolicyScript                = System.Collections.Generic.Dictionary`2[System.String,System.Object];
            DeviceThreatProtectionEnabled               = $True;
            ...
        }

This obviously doesn't compile and never worked (probably since the beginning). Yet, nobody bothered with this property not working. With this PR, the export will look like the following:

IntuneDeviceCompliancePolicyWindows10 "IntuneDeviceCompliancePolicyWindows10-IntuneDeviceCompliancePolicyWindows10_1"
        {
            ...
            Description                                 = "";
            DeviceCompliancePolicyScript                = MSFT_MicrosoftGraphDeviceCompliancePolicyScript{
                RulesContent = "<JSON Content of the rules>"
                DisplayName = "IntuneDeviceComplianceScriptWindows10_1 (TODO)"
            };
            DeviceThreatProtectionEnabled               = $True;
            ...
        }

This corresponds to the following Custom compliance setting in the policy:

Yes, you are right, under normal circumstances, this would absolutely be a breaking change. But I don't think that's the case here since the export never was correct and even if anything was specified, it would never have worked with this property specified. So I think it's fair to assume we can change it without a breaking change release.