Support OpenSSL 4.0

[vcsjones]

There are some changes that are going to be needed to support OpenSSL 4.0 when it is released, which is expected sometime in the spring.

• Teach OpenLibraryOnce about the .4 so object suffix.
• For portable builds with 3.0 headers, we need to teach it about OPENSSL_sk_set_thunks so that .NET Build against 3.0 headers functions correctly against 4.0
• There have been a number of pull requests to fix compilation against 4.0 headers, primarily that some things have been const-ified. We should decide what, if anything, gets back ported and to where.

[dotnet-policy-service]

Tagging subscribers to this area: @bartonjs, @vcsjones, @dotnet/area-system-security
See info in area-owners.md if you want to be subscribed.

[vcsjones]

OpenSSL 4.0 was released yesterday. I believe this is the list of PRs to get OpenSSL 4.0 support working.

• Fix build compilation with OpenSSL 4.0-dev. #122744
• Enable the crypto shim to build against OpenSSL 4.0-alpha1 headers #125470
• Allow binding to OpenSSL 4 from portable builds #125687

TODO:

1. Decide where 4.0 fits in the loading order. Right now it is last.
2. We don't have an image In CI for this. Typically Alpine is one of the first to get newer versions of OpenSSL, LTS or not.