add msquic to Alpine Helix image

[wfurt]

This is similar to what we do for fedora/34. There is no package so we build msquic from our clone.
This change should allow us to run HTTP/3 & Quic tests on Alpine.
We may need to update this when MsQuic has new release (and we update our clone)

contributes to dotnet/runtime#55639

I was also looking to add it to arm64 but there is no PowerShell so we would either need to compile it from sources or somehow avoid use of pwsh.

[rzikm]

Should we use -UseSystemOpenSSLCrypto?

[wfurt]

We could. I don't think it matters much as this is used only by this one particular image. It would probably produce slightly smaller binary.

[rzikm]

LGTM, modulo one question

[mthalman]

I was also looking to add it to arm64 but there is no PowerShell so we would either need to compile it from sources or somehow avoid use of pwsh.

For reference, there is an existing issue for Alpine-based Arm64 support at PowerShell/PowerShell#12937.

To work around this, you can use a multi-stage Dockerfile to build msquic in a non-Alpine-based stage and copy the resulting binaries to the final Alpine-based stage.

[mthalman]

Is there any reason not to apply these changes to the Alpine 3.15 Dockerfile instead? Is there anything that restricts you from consuming Alpine 3.15? The Dockerfiles are identical except for the Alpine version. That would give you 6 months extra of a supported OS.

[wfurt]

Is there any reason not to apply these changes to the Alpine 3.15 Dockerfile instead?

Not really. I look at what runtime uses for testing now and that was 3.14. Maybe I can add it to 3.15 as well but I did not want to change OS version just to add MsQuic. I can do that as follow-up if we get stable CI. (so as arm architectures)