UniSocket mode is unreliable [API-1276] #595
Description
In some situations, the UniSocket mode in 5.0.0 and 5.0.1 client is known to become unreliable.
This happens when the configured connection address (say, 10.0.0.1) is not the address that is reported by the member we connect to (say it reports 10.0.0.2), which currently causes us to close the original connection (to 10.0.0.1) and rely on our re-connection mechanism to establish a connection to 10.0.0.2. In UniSocket mode, this re-connection mechanism does not run, and so the client never connects.
We probably need to activate that re-connection mechanism for UniSocket too, while making sure it only maintains one active connection for the client (and does not connect to all members). We probably also want to investigate how the UniSocket mode client reconnects in case it gets disconnected. And, maybe it's worth discussing what to do exactly when the addresses reported by the cluster don't match the configured addresses.