Integrate validation routine into SPAM core

[kuqin12]

Preface

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

Description

The current code does not use the validation routine from newly introduced responder code, causing a few misses on the linked symbols and optimized PCDs.

This change will use the routine in SPAM core and thus pulling in a few functional changes in the page table functions.

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, ...
• [ ] 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

This change is tested to be buildable.

Integration Instructions

N/A

[kuqin12]

Needs https://github.com/microsoft/mu_feature_mm_supv/pull/277 to complete first.

[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@2794f5d). Click here to learn what that means.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## feature/spam #278 +/- ## ============================================== Coverage ? 0.46% ============================================== Files ? 144 Lines ? 22348 Branches ? 60 ============================================== Hits ? 105 Misses ? 22238 Partials ? 5 ``` | [Flag](https://app.codecov.io/gh/microsoft/mu_feature_mm_supv/pull/278/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/278/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.