Use ReconnectingSocket in Tendermint and Ethereum

[willclarktech]

Closes #229

Opening a draft PR to discuss API. In particular, the EthereumConnection tests call socket.disconnect() but currently if you do this on ReconnectingSocket before the connection has been successfully established you get an error. Should this be changed or should the higher-level WS clients expose a stream of connection statuses?

[webmaster128]

Should this be changed or should the higher-level WS clients expose a stream of connection statuses?

I think calling

      const socket = new ReconnectingSocket(socketServerUrl);
      socket.connect();
      socket.disconnect();

should be valid, especially since it is hard for an application to know when the connection was established. I think this.unconnected should be changed to just guard against wrong order of calls, like double connect() or disconnect() without connect(), which indicate programming errors.

There is a test "can disconnect before waiting for open" in packages/iov-socket/src/socketwrapper.spec.ts and I think a similar test should pass for ReconnectingSocket as well.

[webmaster128]

Why this signature change? This requires the caller to set ignoreNetworkError to something. If we want that, we can remove the undefined option.

[willclarktech]

Whoops, originally removed the parameter entirely then added it back in with the compiler's suggestion.

[webmaster128]

await this.socket.connectionStatus.waitFor(ConnectionStatus.Connected)

This does what you implement below and also resolves when the value is ConnectionStatus.Connected already.