Drop non-shared crypto from QemuQ35Pkg and QemuSbsaPkg

[makubacki]

Description

Moving forward the OpenSSL submodule will no longer be present in
CryptoPkg and the only option to integrate crypto into the platform
will be shared crypto (via the binary crypto ext dep).

The option to enable/disable shared crypto is removed since disabling
it is no longer an option.

Notes:

• Integrates newly available AARCH64 PEI and Standalone MM shared crypto binaries.

• The BaseCryptLibUnitTest EFI shell test is removed since it depends on
  functions not present in the PPI/Protocol instances of BaseCryptLib and
  the crypto releases should have the tests run before the release is made.

  • An issue to track this is here: [Feature]: Run BaseCryptLib Unit Test (EFI Shell tests) in this Repo mu_crypto_release#56

• Runtime DXE crypto is not currently available. It is only needed at this time for
  the non-SMM instance of QemuQ35Pkg (VariableRuntimeDxe). Since this is not the
  primary target for QemuQ35Pkg, the Runtime DXE binary will be updated in the
  future to unblock Mu Basecore updates in Mu Tiano Platforms.

  • An issue to track that is here: [Feature]: Add Runtime DXE shared crypto support mu_crypto_release#55

---

Updates these submodules to the following release points:

• MU_BASECORE: v2023020013.1.0

• Common/MU_TIANO: v2023020000.2.0

• Features/MM_SUPV: v8.1.8

---

• 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

• QemuQ35Pkg and QemuSbsaPkg CI build and boot.

Integration Instructions

• These changes only affect the mu_tiano_platforms.

[makubacki]

Now just waiting on microsoft/mu_basecore#715 to complete.

[makubacki]

Now just waiting on microsoft/mu_basecore#715 to complete.

Done. The PR has all changes now.