QLocalSocket/Win: state is different from Unix platforms after connection loss

After noticing a broken pipe in a reading QLocalSocket, which still has data in its internal read buffer, the state of this socket should immediately go to Unconnected.
This is the behaviour on Unix.

Also, methods like waitForReadyRead and so on have different return types on Unix / Win in this case.