(Android) WebSocketClient initialization hangs when connecting to a resource that is currently unavailable but was connected to before.

If the resource that WebSocketClient was previously connected to becomes unavailable, WebSocketClient initialization hangs. Instead of returning a connection error. Testing was conducted only on Android

Start at WebSocketClient initialization and reproduce the unavailable-resource case on Android, comparing it with a first-time connection. Trace why initialization waits instead of returning a connection error; done means the previously connected but unavailable resource reports an error rather than hanging.

Written by the indexing model from the issue text.