DO NOT MERGE - Async networking

[LimpidCrypto]

High Level Overview of Change

Adds async networking abilities:

• AsyncWebsocketClient
• AsyncJsonRpcClient

Due to the milestones complexity, a new crate em-as-net will be created. For a high level overview of the state of em-as-net see this issue:

• #1

Important to notice: At the time of writing the crate is still missing TlsConnection to establish safe connections.

The PR also contains smaller improvements like making ˋnewˋ methods public and importing the ˋToStringˋ trait in the ˋErr!ˋ macro instead of importing it in every file that uses the macro.

TODO

• no_std support for clients here in xrpl-rust and in em-as-net
• Establish safe connections using TlsConnection in em-as-net

Type of Change

• New feature (non-breaking change which adds functionality)

Test Plan

A code sample was added to tests/common.rs

[LimpidCrypto]

I still have an issue with the github workflow, claiming that it can't find xrpl::asynch::clients and rand::rngs::ThreadRng:

error[E0432]: unresolved import `rand::rngs::ThreadRng`
 --> tests/common/mod.rs:4:5
  |
4 | use rand::rngs::ThreadRng;
  |     ^^^^^^^^^^^^^^^^^^^^^ no `ThreadRng` in `rngs`
error[E0432]: unresolved import `xrpl::asynch::clients`
 --> tests/common/mod.rs:6:19
  |
6 | use xrpl::asynch::clients::{
  |                   ^^^^^^^ could not find `clients` in `asynch`
error[E0432]: unresolved import `xrpl::asynch::clients`
 --> tests/integration/clients/mod.rs:6:23
  |
6 |     use xrpl::asynch::clients::{ReadResult, WebsocketClose, WebsocketIo};
  |                       ^^^^^^^ could not find `clients` in `asynch`

[sephynox]

Do we want to do this?

[sephynox]

Should we allow these exceptions?

[LimpidCrypto]

I allowed too_many_arguments because the new methods have a lot of parameters. What would be your suggestion to resolve the clippy warning?

[LimpidCrypto]

Closed in favor of #70