Feature parity with `electrum_client`

[evanlinjin]

electrum_streaming_client is already a lot more flexible than electrum_client as it uses a sans-IO architecture internally.

However, electrum_streaming_client's Client and AsyncClient requires the caller to provide their own transport (which can mean a lot of boilerplate). In electrum_client, the transport construction is handled internally.

Proposal

Implement both async/sync transport types that are easy to construct for the following connection types:

• TCP
• SSL
• Tor
• Socks5

[oleonardolima]

Also, as it's being worked on bitcoindevkit/rust-electrum-client#194 we'd need authentication/authorization support too.