ProcessMitigation ResourceID is created in an inconsistent format

[mapresto]

Describe the bug ResourceID and InstanceName for ProcessMitigation rules for Windows 10 stig are not in the standard format.

Current output is: [ProcessMitigation]AcroRd32.exe-V-77191::[WindowsClient]Client

Expected output would be: [ProcessMitigation][V-77191][medium][WN10-EP-000080]::[WindowsClient]Client

To Reproduce Create MOF based on Windows 10 composite resource. Assuming the mof file path is save to $testPath run the following:

$TestResults = Test-DSCConfiguration -ComputerName Win10Test -ReferenceConfiguration $testPath $FullResults = $TestResults.ResourcesInDesiredState + $testResults.ResourcesNotInDesiredState $fullResults | select ResourceID

Expected behavior Expected output would be: [ProcessMitigation][V-77191][medium][WN10-EP-000080]::[WindowsClient]Client

Screenshots

Additional context I am using the ResourceName and/or InstanceName to determine scan results using PowerStig. For the majority of resources this holds the majority of the information that I need on the fly but for the ProcessMitigation rules, the parsing that I am using would need to be rewritten to support just these rules, and it still would not hold all of the information that I would normally gather.

[athaynes]

@mapresto I am updating the resource call to use the standard formatting function. That being said, the rules for V-77091,95,97,101, and 103 have a duplicate key in the resource (MitigationTarget), so they get merged together. I'll need to think on this a little bit.