crypto/x509: TestPlatformVerifierLegacy/expired_leaf failures

[gopherbot]

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/expired_leaf"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestPlatformVerifierLegacy/expired_leaf
    root_windows_test.go:102: tls connection failed: dial tcp 104.154.89.105:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestPlatformVerifierLegacy/expired_leaf (21.20s)

— watchflakes

[gopherbot]

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/x509" && test == "TestPlatformVerifierLegacy/expired_leaf"

2024-05-13 21:10 go1.22-windows-amd64-longtest release-branch.go1.22@d4a81ec7 crypto/x509.TestPlatformVerifierLegacy/expired_leaf (log)

=== RUN   TestPlatformVerifierLegacy/expired_leaf
    root_windows_test.go:102: tls connection failed: dial tcp 104.154.89.105:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
--- FAIL: TestPlatformVerifierLegacy/expired_leaf (21.20s)

— watchflakes