add libmsquic to to Helix queues with OpenSSL 1.1 (After 8/5/2022)

• This issue is blocking
• This issue is causing unreasonable pain

This contributes to https://github.com/dotnet/runtime/issues/55639

So far, we have only Linux testing on Fedora x64. Since we are going to support HTTP/3 (that depends on Quic) in .NET 7, we should improve test coverage.

This was not done, because there are no sufficient packages of MsQuic as of now. MsQuic should cut 2.1 release for us by end of the week and we should have signed deb and rpm packages available on packages.microsoft.com shortly after.

The actually work consist of two steps:

1. adding packages.microsoft.com as source to given distributions. (unless already there) Example notes can be found here: https://docs.microsoft.com/en-us/dotnet/core/install/linux (we generally need to add the signing key and repo location)

2. use package manager to install MsQuic. For example ‘apt install libmsquic’.

Note that MsQuic depends on OpenSSL 1.1 so we may have problems on distributions where OpenSSL 3.0 is the default. I think for now, we can skip them, active investigation into compatibility is in happening.

BTW there is currently no support of macOS packages and it will be addressed separately.

cc: @karelz

[rzikm]

CentOS 7 has too old OpenSSL, so that is not going to work.

@wfurt I don’t think there is more we need as part of this issue, so I am closing it again.

[MattGal]

I verified this is in at least the following Helix images and all related internal/public versions of them

centos.7.amd64 redhat.7.amd64 sles.12.amd64 sles.15.amd64 ubuntu.1604.amd64 ubuntu.1804.amd64 ubuntu.2004.amd64 ubuntu.2204.amd64

Moving to rollout. @wfurt is trying to run the tests against the staging environment and we can do some experiments with this tomorrow if that doesn’t work out.