Split MM PEI IPL into normal IPL and MM Supervisor PEI Support

[kuqin12]

Description

This change splits the MM supervisor communication PPI into its own module rather than a combined MM PEI IPL driver.

This will allow the adoption of the StandaloneMmPeiIpl from EDK2 for X64 platforms.

For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

• Impacts functionality?
• Impacts security?
• Breaking change?
• Includes tests?
• Includes documentation?

How This Was Tested

This was tested on QEMU Q35 virtual platform.

Integration Instructions

Add MmSupervisorPkg/Drivers/MmPeiLaunchers/MmPeiSupport.inf to platform dsc and fdf file.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 145 lines in your changes missing coverage. Please review.
✅ Project coverage is 0.52%. Comparing base (0d068c0) to head (8272fa2).

Files with missing lines	Patch %	Lines
...upervisorPkg/Drivers/MmPeiLaunchers/MmPeiSupport.c	0.00%	122 Missing ⚠️
MmSupervisorPkg/Drivers/MmPeiLaunchers/MmIplPei.c	0.00%	23 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #577      +/-   ##
========================================
- Coverage   0.52%   0.52%   -0.01%     
========================================
  Files        132     133       +1     
  Lines      20067   20126      +59     
  Branches      60      60              
========================================
  Hits         106     106              
- Misses     19956   20015      +59     
  Partials       5       5              

Flag	Coverage Δ
MmSupervisorPkg	0.52% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kuqin12]

Needs #585 to complete first.

[mu-automation]

This PR has been automatically marked as stale because it has not had activity in 60 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

[mu-automation]

This pull request has been automatically been closed because it did not have any activity in 60 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

[kuqin12]

not stale...

[mu-automation]

This PR has been automatically marked as stale because it has not had activity in 60 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

[mu-automation]

This pull request has been automatically been closed because it did not have any activity in 60 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

[kuqin12]

need to rebase the commits, but the idea did not change that we want to split the current IPL into 2 so that the user and supv communication channels are separate.