Add a test for validation routine to be used in supervisor core

[kuqin12]

Preface

Please ensure you have read the contribution docs prior to submitting the pull request. In particular, pull request guidelines.

Description

This change added a test handler into the MM supervisor core to facilitate the testing of SPAM core validation in-situ.

The test handler will be registered at the entry point of MM core and the Shell test app will communicate to the supervisor to trigger the validation routine and return the policy and measurement digests.

For each item, place an "x" in between [ and ] if true. Example: [x]. (you can also check items in the GitHub UI)

• [x] Impacts functionality?
  • Functionality - Does the change ultimately impact how firmware functions?
  • Examples: Add a new library, publish a new PPI, update an algorithm, ...
• [ ] Impacts security?
  • Security - Does the change have a direct security impact on an application, flow, or firmware?
  • Examples: Crypto algorithm change, buffer overflow fix, parameter validation improvement, ...
• [ ] Breaking change?
  • Breaking change - Will anyone consuming this change experience a break in build or boot behavior?
  • Examples: Add a new library class, move a module to a different repo, call a function in a new library class in a pre-existing module, ...
• [x] Includes tests?
  • Tests - Does the change include any explicit test code?
  • Examples: Unit tests, integration tests, robot tests, ...
• [ ] Includes documentation?
  • Documentation - Does the change contain explicit documentation additions outside direct code modifications (and comments)?
  • Examples: Update readme file, add feature readme file, link to documentation on an a separate Web page, ...

How This Was Tested

Tested on QEMU Q35.

Integration Instructions

• The platform build needs to link NULL|SpamPkg/Core/Test/ResponderValidationTestLib.inf into MmSupervisorCore.inf.
• Set the feature PCD MmSupervisorPkgTokenSpaceGuid.PcdMmSupervisorTestEnable to TRUE.
• Set gEfiSpamPkgTokenSpaceGuid.PcdSpamMeasurementPcrIndex to 0 to allow normal measurement from inside MM.
• Then adding SpamPkg/Tests/ResponderValidationTest/ResponderValidationTestApp.inf to the dsc and fdf file.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (feature/spam@85e7e35). Click here to learn what that means.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## feature/spam #285 +/- ## ============================================== Coverage ? 0.46% ============================================== Files ? 144 Lines ? 22349 Branches ? 60 ============================================== Hits ? 105 Misses ? 22239 Partials ? 5 ``` | [Flag](https://app.codecov.io/gh/microsoft/mu_feature_mm_supv/pull/285/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=microsoft) | Coverage Δ | | |---|---|---| | [MmSupervisorPkg](https://app.codecov.io/gh/microsoft/mu_feature_mm_supv/pull/285/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=microsoft) | `0.46% <ø> (?)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=microsoft#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.