Make SSL handshake exceptions and logging useful

[wfurt]

There is growing number of cases (like #27703) where uses see something like:

---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)

From that, it is very difficult to diagnose real root cause
It would be nice if the exception can provide more specific reason. This may not be complete list but it would be nice to distinguish following cases:

• wrong time
• unknown/untrusted CA
• name mismatch
• CRL/OSCP revocation issues
• custom verification callback denial
• extended key usage violation or other attribute problems

[karelz]

@wfurt just one area label please ;)

[wfurt]

I don't understand your question @weitzhandler. This issue is about improving text but it will not change the behavior anyhow.
If you are failing to connect, you need to check your trust chain. Alternatively, you can can register validation delegate and process it your self.

[karelz]

One concrete example is in #29518