Increase network read timeout when sending transactions

[NicolasFlamel1]

A followup to my previous pull request #15 that I accidentally closed by rebasing my fork.

These changes increase the network read timeout to 5 minutes when sending transactions to avoid timing out too early when exchanging a slate with a device that takes longer than a few seconds to generate a reply.

The 5 minute timeout is now only applied when sending a receive_tx request, and all other request types will still use the existing default read timeout. This will avoid any unnecessary waiting since a check_version request always comes before a receive_tx request.

[vekamo]

Looks great 👍 I'm wondering tho if that wouldn't be better to implement a field in check_version that indicate whether or not the device could take longers to give the slate response. Such as low_hardware: true which would mean the sender can await a response within 5, 10 min etc. Will think about this.

[bayk]

I am testing now send requests works. From what I see, timeout is need to address tor possible connection issue. The timeout value should depend on the network speed, that mostly depend on what platform tor is running. In the Windows seems it is slowest. Plus how long the network was inactive. There is 'check_tor_connection' command that ping the tor. I think we better to run it in the background when wallet is listening with tor. Another problem that wallet might be busy and be locked during the request. That will add to waiting time as well. I think I will implement the background ping and increase the timeout to 180 seconds, 5 minutes is too much. That should be good enough. P.S. Also the http client is different now, there are conflicts, so I will add changes from the scratch.