CryptoPkg: Update shared crypto to 2023.2.8

[makubacki]

Description

Shared crypto binaries in this release include PEI and Standalone MM
AARCH64 builds.

• 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, boot, and tests.
• Also test new AARCH64 binaries on a physical AARCH64 platform.

Integration Instructions

Use the new PEI and Standalone MM AARCH64 binaries if needed for a platform.

[makubacki]

Note: Since 2023.2.7 was built against a personal branch (while a PR was open), for future traceability and audit, I'm rebuilding the same functionally equivalent code over there against release/202302 which now has the change included. That is being published as 2023.2.8.

So, I will push an update to this PR to use 20232.2.8 when the publish pipeline is done.

[makubacki]

So, I will push an update to this PR to use 20232.2.8 when the publish pipeline is done.

Done.