SSLClient verifies the server certificate chain with CryptoAPI on
Windows by default, while WebSocketClient always left it to the TLS
backend, whose snapshot of the Windows store lacks the roots Windows
fetches on demand. A wss:// connection could fail against a host that
SSLClient connects to.
WebSocketClient now makes the same decision through a shared helper,
and gets enable_windows_certificate_verification() to turn it off.
Fix#2685