re-enable TLS 13 tests on Windows

[wfurt]

While the underlying issue lives in Schannel and it is being fixed in Windows the root analyses points to certificates with CAPI provider. That works fine for previous TLS versions but it fails for TLS 1.3 as that is somehow different.

This change brings new pfx files from dotnet/runtime-assets#234
With updated data (essentially still same certificate) everything seems to be stable.

This is only fix for the

---- System.ComponentModel.Win32Exception : The Local Security Authority cannot be contacted

other (recent server 2022) failures are unrelated to this.

fixes #58927

[ghost]

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

Issue Details

---

While the underlying issue lives in Schannel and it is being fixed in Windows the root analyses points to certificates with CAPI provider. That works fine for previous TLS versions but it fails for TLS 1.3 as that is somehow different.

This change brings new pfx files from dotnet/runtime-assets#234
With updated data (essentially still same certificate) everything seems to be stable.

This is only fix for the

---- System.ComponentModel.Win32Exception : The Local Security Authority cannot be contacted

other (recent server 2022) failures are unrelated to this.

fixes #58927

Author:	wfurt
Assignees:	wfurt
Labels:	area-System.Net.Security, test-enhancement
Milestone:	-

[rzikm]

LGTM

[wfurt]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wfurt]

test failures are #67682, #67685 and perhaps others. #68083 should fix the Server 2022 failures. I did not see any The Local Security Authority cannot be contacted. I'll keep watching the runs.