QSslSocket test - adapt 'verifyClientCertificate' for Secure Transport

Secure Transport relies on keychains, both client/server are constantly
updating default keychain and as a result tests are failing: when
verification is expected to fail, it succeeds; when the number of certificates
is expected to be 1 - it's 2 (Secure Transport can find certificates in a keychain).
This makes verifyClientCertificate test quite useless at the moment - QSKIP it.

Change-Id: I578398b4912a86dc60f585ac5a1bdd0098914005
Reviewed-by: Richard J. Moore <rich@kde.org>

tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp

@@ -2871,6 +2871,14 @@ void tst_QSslSocket::verifyClientCertificate_data()
 
 void tst_QSslSocket::verifyClientCertificate()
 {
+#ifdef QT_SECURETRANSPORT
+    // We run both client and server on the same machine,
+    // this means, client can update keychain with client's certificates,
+    // and server later will use the same certificates from the same
+    // keychain thus making tests fail (wrong number of certificates,
+    // success instead of failure etc.).
+    QSKIP("This test can not work with Secure Transport");
+#endif
     if (!QSslSocket::supportsSsl()) {
         qWarning("SSL not supported, skipping test");
         return;