feat(wallet): Add a vertex history streamer to the wallet websocket API

[msbrogli]

Motivation

Wallets might need to download their transaction history. The full node currently offers a polling API but this is too slow to both large wallets and high latency environments. This PR implements a streaming API that speeds up the download for wallets.

Streaming protocol

Client sends either request:history:xpub or request:history:manual.
Server open the streaming and follows the documented protocol (see the streamer docustring).

Performance

Testing with a wallet that has 1,060 addresses and 1,187 transactions with 480ms of latency between the wallet and the full node.

Download time

• Polling API: 17,764ms
• XPub Streamer: 3,284ms
• Manual Streamer: 2,893ms

Total time (including a post-processing that occurs after the download):

• Polling API: 27,336ms
• XPub Streamer: 13,189ms
• Manual Streamer: 13,551ms

Notice that the post-processing time is the same for all APIs (~10 seconds).

Acceptance Criteria

1. Refactor HathorAdminWebsocketFactory.handle_message(), moving it to HathorAdminWebsocketProtocol.
2. Refactor HathorAdminWebsocketFactory._handle_ping(), moving it to HathorAdminWebsocketProtocol.
3. Add HathorAdminWebsocketFactory.subscribe_address(), which subscribes the connection to receive real time updates for all vertices related to an address.
4. Add the websocket message request:history:xpub, which opens a streaming generating addresses from the xpub and stopping when the GAP limit is reached.
5. Add the websocket message request:history:manual, which opens a streaming from a list of addresses and stopping when the GAP limit is reached or the list of addresses ran out.
6. Add the websocket message request:history:stop, which stops the current streamer.
7. Only one streaming at a time per websocket connection.
8. Set the maximum list of pending addresses in request:history:manual to 5,000 addresses per connection.
9. Add a capabilities message when a new websocket connection is opened.
10. Add a --disable-ws-history-streaming argument to the run_node cli command.
11. Add a disable_history_streaming() to the factory that disables history streaming in all connections too.
12. Add a disable_history_streaming() to the protocol that stops the streaming if one is opened.

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged