Replace VerifyWithRevocation test with DynamicRevocationTests

[vcsjones]

VerifyWithRevocation is a flaky test. It needs internet to contact a CA for CRL/AIA and can occasionally fail. This replaces the offline revocation checking part of that test with DynamicChainTests which use our own local CA.

Fixes#41952

[ghost]

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @jeffhandley
See info in area-owners.md if you want to be subscribed.

[vcsjones]

Some justification:

I ran VerifyWithRevocation on an ARM64 AWS instance a few thousand times, dumping the CRL and OCSP cache between each run by deleting ~/.dotnet/corefx/cryptography/crls and ~/.dotnet/corefx/cryptography/ocsp. I was unable to get it to fail with a stable network connection, so I am not aware of an actual underlying issue that the test is catching.

[vcsjones]

This could use an outerloop run when anyone has a moment: /azp run runtime-libraries-coreclr outerloop

[bartonjs]

/azp run runtime-libraries-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[bartonjs]

None of the failures in HTTP (which look to be various kinds of timeouts) should have been caused by this test-only change (at least, it's not obvious that the timeouts are caused by some sort of automagical call to RevocationResponder.Stop()), so merging.

[vcsjones]

@bartonjs I don't know what the bar is for porting test enhancements, but would it make sense to port this and perhaps #42680 to release/5.0 to stabilize the branch?