Support the SymCrypt provider for OpenSSL

[qmuntal]

This is an umbrella issue to track support for the SymCrypt provider for OpenSSL (SCOSSL). SCOSSL is the the default provider in Azure Linux 3, so we (the Microsoft maintainers of golang-fips/openssl) are very much interested on supporting SCOSSL as a first class target.

SCOSSL does not implement all algorithms supported by this repo, e.g. HMAC-SHA224, and also makes some assumptions that are incompatible with how we use the OpenSSL API. We should revist our assumptions and fix whatever needs fixing.

List of known issues/tasks:

• Add Azure Linux 3.0 coverage in GitHub Actions #154
• Avoid SymCrypt provider logs in TestECDSASignAndVerify #155
• Return nil in NewHMAC if HMAC doesn't support the hash function #159
• Only implement encoding.BinaryMarshaler for hashers provided by built-in providers #161
• Only omit RSA primes if precomputed values are missing in OpenSSL 3.0 and 3.1 #163
• Implement Clone for all hashers #167
• Fix TestHMAC when using the SymCrypt provider #175
• Fail CI pipeline if azurelinux job fails #178
• Refactor openssl.FIPS to support third-party FIPS providers #184
• Make algorithms more robust to unsupported hashes #185
• Only implement the supported AES extra mode interfaces #186
• Implement SupportsDSA #187
• Make SupportsHKDF provider-aware #188
• Implement TLS1 PRF using the EVP_KDF API in OpenSSL 3 #191
• Implement HKDF using the EVP_KDF API in OpenSSL 3 #194
• Refactor SetFIPS to support third-party FIPS providers #206
• Implement SupportsPBKDF2 #207
• Implement HasFIPSProvider #211

[qmuntal]

Done!