Ignore revocation checking failures on HTTPS tests on OSX

[rzikm]

This PR applies similar fix as in #22644 to Outerloop HTTPS tests where we check exact certificate validation errors. Additional context is also available at #25872

[Copilot]

Pull Request Overview

This PR enhances logging for certificate validation errors in the HttpClientHandler tests by outputting detailed information about each certificate in the chain along with associated error statuses.

• Added a loop to iterate through all certificate chain elements and output certificate details and status information.
• Logged overall SSL policy errors at the end of the callback.

[rzikm]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rzikm]

/azp run runtime-libraries-coreclr outerloop-osx

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rzikm]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rzikm]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dotnet-policy-service]

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

[wfurt]

are we forcing customers to basically do the same?

[rzikm]

are we forcing customers to basically do the same?

for customers, the right way to fix this would be disabling certificate revocation checking, but it is true that this might start affecting more people than we originally expected. I am wondering if we should consider different default for OSX.

cc @bartonjs, @blowdart for visibility.

[rzikm]

I added a mention about ignoring revocation status unknown status when building the chain to the breaking change doc.