Configuration processor auditing improvements

[JohnMcPMS]

Change

When a processor path is provided, inform the user about that fact in the output. Ensure that the server agrees on the hash of the processor that is provided in its CLI arguments.

When the target processor is an app execution alias, the hash is of the contents of the reparse point data. Otherwise, it is a hash of the contents of the file itself.

Custom processor path:
  Path: C:\Program Files\WindowsApps\Microsoft.DesiredStateConfiguration_3.2.0.0_x64__8wekyb3d8bbwe\dsc.exe
  Hash: 6ee88bd4c93c4a94539a0af0667ace8ffba48f5b8732930e1421721621ca19de
  Signed By: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

Validation

Tests are added for the scenario and individual operations.

Microsoft Reviewers: Open in CodeFlow

[florelis]

I'm not familiar with the configuration code, so my review of that part was superficial and it may be wise to get somebody else to look at it.

[florelis]

Should we move all the .mds here?

[florelis]

Could we extract the signer/publisher from the package that owns the alias?

[JohnMcPMS]

We don't know that with OS APIs. We could infer things about the path and likely find the family name, then the full name, then extract the signing information. But all of that is a guess, and a bad actor could easily replace the alias contents while we claimed signature information from the other package.