fix output of Assertion resource for test to resemble config and add support for array comparison

[SteveL-MSFT]

PR Summary

Two problems addressed by this PR:

• The output of Assertion simply returned the actual result to look like a get result, however, this causes the synthetic test doing a diff to fail as they don't resemble each other. To address this, added a new hidden switch --as--config to inform dsc that this is a special case and the output needs to be transformed to a Configuration so that the synthetic test can work.

Here's example of the new output:

metadata:
  Microsoft.DSC:
    version: 3.0.0
    operation: Test
    executionType: Actual
    startDatetime: 2024-11-07T16:45:48.237829-08:00
    endDatetime: 2024-11-07T16:45:48.789203-08:00
    duration: PT0.551374S
    securityContext: Restricted
results:
- metadata:
    Microsoft.DSC:
      duration: PT0.441752S
  name: Operating System Assertion
  type: Microsoft.DSC/Assertion
  result:
    desiredState:
      $schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2023/08/config/document.json
      resources:
      - name: Is64BitOS
        type: Microsoft/OSInfo
        properties:
          bitness: '64'
      - name: 64bit test 2
        type: Microsoft/OSInfo
        properties:
          family: Windows
    actualState:
      $schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/config/document.json
      resources:
      - type: Microsoft/OSInfo
        name: Is64BitOS
        properties:
          $id: https://developer.microsoft.com/json-schemas/dsc/os_info/20230303/Microsoft.Dsc.OS_Info.schema.json
          family: macOS
          version: 15.1.0
          bitness: '64'
          architecture: arm64
      - type: Microsoft/OSInfo
        name: 64bit test 2
        properties:
          $id: https://developer.microsoft.com/json-schemas/dsc/os_info/20230303/Microsoft.Dsc.OS_Info.schema.json
          family: macOS
          version: 15.1.0
          bitness: '64'
          architecture: arm64
    inDesiredState: false
    differingProperties:
    - resources
messages: []
hadErrors: false

• The second issue is that the synthetic test didn't handle arrays at all and resources is always an array. Arrays need to be the same per the current diff rules:
  • same size
  • each element needs to exist
  • objects in actual can be superset of the expected

PR Context

Fix #165