QAbstractSocket::waitForConnected() shouldn't abort the connection process after the timeout has elapsed.

Documentation for QAbstractSocket:.waitForConnected() says "If the function times out, the connecting process will be aborted."
and indeed the source seems to suggest that when the timeout is reached the socket layer is forcibly reset.

This makes aborting cleanly a slave thread that is stuck in a long waitForConnected() call impossible: the application will just
hang until waitForConnected() exits. If one could call waitForConnected() with small timeouts repeatedly without resetting
the connection the problem would be solved.

Alternatively it should be possible to call abort() from a different thread for waitForConnected() to exit.