[release/6.0] make sure OpenSSL is initialized before Tls13Supported code runs

[wfurt]

This back port of #62973

Fixes#61891

Customer Impact

Customer reported regression. When customer uses class System.Net.Security.CipherSuitesPolicy early in the process it will throw exception and it will also prevent ANY further usage of TLS 1.3 in that process.

The root cause is bad dependency of static constructors which won't initialize OpenSSL in time. TLS 1.3 detection will fail without initialized OpenSSL and the (failed) result will be stored in a static variable.

Regression

Yes, it was introduced in 6.0

Testing

Testing was manual as the behavior depends on loading native ship and sequence of operations - both happen before our test even start. I used the sample code from #62973 and debugger to verify that the property is properly set.

Risk

Small. This basically makes sure OpenSSL is initialized before we use it.

[ghost]

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

Issue Details

---

This back port of #61891

Customer Impact

The issue described in #61891 impacts use of CipherSuitesPolicy. However the Tls13Supported is internal static properly and when incorrectly set to false it prevents application from using Tls1.3

Regression

yes. This was introduced in 6.0

Testing

Testing was manual as the behavior depends on loading native ship and sequence of operations - both happen bore our test even start. I used the sample code form #62973 and debugger to verify that the properly is properly set.

Risk

small. This beasicly makes sure OpenSSL is initialized before we use it.

Author:	wfurt
Assignees:	-
Labels:	Servicing-consider, area-System.Net.Security
Milestone:	6.0.x

[wfurt]

SendPacketsElement_FileLargeOffset_Throws on Windows is unrelated. ( #63888)
Mono failure is #57941