[release/6.0] add TLS 1.3 support to WinHttp

[github-actions]

Backport of #58590 to release/6.0

WinHttp now has and the flag and it seems to work right on Windows 11

#define WINHTTP_FLAG_SECURE_PROTOCOL_TLS1_3 0x00002000

.NET Framework 4.8 now supports Tls13 as well somebody can use it with casting int like the test change.
It really does not matter as long as running on supported OS and WinHttp as all the work is done by native code.

Fixes #58587

/cc @karelz @wfurt

Customer Impact

Users of WinHttpHandler cannot use TLS1.3 on Win11+ (where the OS supports it).
We would need to release WinHttpHandler NuGet package patch (via servicing of .NET 6) once Win11 is public.

Testing

TODO: Win11 test run - @wfurt

Risk

Low. The component only sim-ships with .NET 6 as a standalone NuGet package.
The change only sets a flag on WinHttp (if it is supported).

[karelz]

Pending green CI & manual Win11 verification.

[karelz]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[karelz]

Unrelated infra problems:

• System.ComponentModel.Composition.Registration.Tests - tests passes, yet job failed

  Discovering: System.ComponentModel.Composition.Registration.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.ComponentModel.Composition.Registration.Tests (found 98 of 130 test cases)
  Starting:    System.ComponentModel.Composition.Registration.Tests (parallel test collections = on, max threads = 4)
  Finished:    System.ComponentModel.Composition.Registration.Tests
=== TEST EXECUTION SUMMARY ===
   System.ComponentModel.Composition.Registration.Tests  Total: 98, Errors: 0, Failed: 0, Skipped: 0, Time: 1.505s
/private/tmp/helix/working/AFBC09DD/w/A0980903/e
----- end Mon Sep 6 07:26:42 PDT 2021 ----- exit code 0 ----------------------------------------------------------
exit code 0 means Exited Successfully
... (more lines in the log) ...

• System.Net.Http.Unit.Tests - tests cut off, no tests listed or test result:

  Discovering: System.Net.Http.Unit.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Http.Unit.Tests (found 892 test cases)
  Starting:    System.Net.Http.Unit.Tests (parallel test collections = on, max threads = 4)
(end of log)

• System.Text.Encodings.Web.Tests - tests cut off, no tests listed or test result:

  Discovering: System.Text.Encodings.Web.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Text.Encodings.Web.Tests (found 212 test cases)
  Starting:    System.Text.Encodings.Web.Tests (parallel test collections = on, max threads = 4)
(end of log)

@dotnet/dncenghot is it a known infra problem?

Re-running tests ...

[greenEkatherine]

It is on OSX.1013.Amd64.Open
@premun did you see it before?

[greenEkatherine]

all these failures happened on dci-mac-build-086.local, I put it offline

[premun]

I haven't but this is not related to Apple/Android so I wouldn't know.

There were some issues around OSX machines getting their jobs killed - https://github.com/dotnet/core-eng/issues/14085

[greenEkatherine]

I haven't but this is not related to Apple/Android so I wouldn't know.

There were some issues around OSX machines getting their jobs killed - dotnet/core-eng#14085

I see, I will raise ticket for DDFUN to fix that machine then

[karelz]

On re-run we got 3 different test suites stuck on the same machine dci-mac-build-086.local:

• System.Text.Json.Tests
• System.IO.Tests
• System.Collections.Concurrent.Tests

Given all the above, the CI results should be considered passing.
@danmoseley it is ready for your approval & merge.

[danmoseley]

Approved - localized, low risk change to fix mainstream scenario regressing on Windows 11.

[danmoseley]

@karelz not sure when the Windows 11 pipelines will be up. Will someone in your team run all your tests, including Outerloop, with 6.0 bits with this change in place? (I know @wfurt ran many of them in main)

[karelz]

Yes, we plan to run Win11 manually -- I actually wanted to make it testing prereq prior to merging (as todo in top post suggests), but I forgot about it and pinged you for approval prematurely ;( ... sorry for that!
I'll make sure we do it in next few days (@wfurt)