fix: reconnects for websocket connection closed ok and ws-api

[pcriadoperez]

FIX #1608

Issue 1 - Reconnect on ConnectionClosedOk:

• Trigger reconnect when receiving Websocket exception ConnectionClosedOk (binance sometimes returns code = 1000)

Issue 2 - user socket and ws-api socket issues:

1. Shared connection and duplicated read loop - user_socket and ws_api read from the same queue and both had read loops, could cause potential issues
2. Stale references - if ws_api reconnected, user_socket still held references to the old websocket

To fix issue2 implemented subscription queues so that the ws-api reads from the queues