Crypto migration to Openssl 3.0.15

[DorLevi95]

Description

<Include a description of the change and why this change was made.>
Change Openssl version from 1.1.1 to 3.0.15
The main reason for the change is Openssl 1.1.1 reached EOL, thus not getting security fixes. OpenSSL 3.0.15 is OpenSSL LTS version.
The changes in this PR are inspired by Edk2 transition, with adaptations to the MU project structure:
tianocore/edk2#4728
tianocore/edk2#6160

For details on how to complete 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

<Describe the test(s) that were run to verify the changes.>

Integration Instructions

<Describe how these changes should be integrated. Use N/A if nothing is required.>

[DorLevi95]

@microsoft-github-policy-service agree company="Microsoft"

[makubacki]

Hi @DorLevi95, since this is a large PR and draft, I haven't reviewed it yet. However, before its final, can you please provide 1) the tests performed and 2) size and performance impact data on a given platform with relevant and generic details about the platform (e.g. whether AES-NI instructions were tested).

[DorLevi95]

@makubacki The OpenSSL update seems to cause significant increase in the binary sizes.
For example, STANDARD_DEBUG binaries (local build):
Before --> After
CryptoDxe.efi - 1012.50 KB --> 1347KB
CryptoPei.efi - 556.00 KB --> 876KB
CryptoRuntimeDxe.efi - 792.50 KB --> 1087KB
CryptoSmm.efi - 534.00 KB --> 853KB
CryptoStandaloneMm.efi - 534.50 KB --> 856KB

@Flickdm is putting some effort to overcome this by merging the binaries.

About testing, currently it seems to pass the BaseCryptLib UTs. We are putting more efforts to enhance the UTs and also providing a reporting tool to gain more confidence in the built binaries.
We can have more robust tests to apply once we'll have all the pre-requirements described above, checked with the OpenSSL update.