Android: QBluetoothSocket::abort() should not always return Unconnected immediately

As a result of fixing QTBUG-44930 it is possible to receive an Unconnected signal right after an QBluetoothSocket::abort() while the socket is still being opened. The QBluetoothSocket should remain in Closing until the WorkerThread has really finished.

This use case can only triggered when the internal InputThread has not been started and abort() is called.

Two scenarios need to be considered. The running QBluetoothSocket.connect may fail or connect. It it fails the Unconnected() state should be set. If it succeeds the closeJavaSocket() signal should be emitted. Once the Thread has finished the Unconnected state should be set.