[QUIC] Improve MSQuic OS Version detection

[Tratcher]

runtime/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/Internal/MsQuicApi.cs

Lines 144 to 146 in 3be5238

	OperatingSystem ver = Environment.OSVersion;
	if (ver.Platform == PlatformID.Win32NT && ver.Version < new Version(10, 0, 19041, 0))

Environment.OSVersion is an unreliable API that reports old versions for compat purposes. It only reports the correct Win10 version if an app manifest is added. VS and the test runner have this manifest but sample apps and customer apps won't.
https://stackoverflow.com/questions/33328739/system-environment-osversion-returns-wrong-version

We're going to need a different way to check for this support. Worst case we look at the registry.

[am11]

fwiw, dotnet-cli uses this property for dotnet --info, which I think does not rely on the app manifest:

runtime/src/installer/managed/Microsoft.DotNet.PlatformAbstractions/RuntimeEnvironment.cs

Line 16 in cf43585

public static string OperatingSystemVersion { get; } = PlatformApis.GetOSVersion();

[jkotas]

Microsoft.DotNet.PlatformAbstractions package is obsolete.

P/Invoking Ntdll.RtlGetVersionEx is your best bet.

[jkotas]

It only reports the correct Win10 version if an app manifest is added. VS and the test runner have this manifest but sample apps and customer apps won't.

This is considered to be a feature. It is not necessary something you want to "fix".

[am11]

Microsoft.DotNet.PlatformAbstractions package is obsolete.

will its sources be removed and dotnet-cli switch to p/invoke?

Edit: nvm, found the issue tracking it - #3470

[Tratcher]

This is considered to be a feature. It is not necessary something you want to "fix".

This version check is to see if the OS has the right TLS 1.3 support. Http3 will have other opt-in guards to maintain compat. Once a developer opts in, false negatives from this version check are an unnecessary hurdle and support burden.