Improve websockets reconnects

[Lohann]

Description

This PR implements a more robust reconnect strategy for Websocket connections, also replaces the default ethere's WS provider by jsonrpsee, which is the RPC Client used by Subxt and Substrate, this also allows Astar connector to use the same websocket connection both for ethereum and substrate calls.

• Create an adapter between jsonrpsee and ethers.
• Supports eth subscriptions
• Replace WS by jsonrpsee.
• Implement a more robust reconnect strategy
• Implement and test the strategy on Astar and Ethereum connectors
• Unit tests

Adapters

Most of the code on this PR are adapters that allow us to use the same client for Ethereum and Substrate interchangeably.

Adapter	JsonRpsee Trait	Ethers Trait
EthClientAdapter	ClientT	JsonRpcClient
EthPubsubAdapter	SubscriptionT	PubsubClient
EthSubscription	Subscription	NotificationStream
EthError	Error	RpcError
EthRpcParams	ToRpcParams	Serialize

Reconnect Strategy:

• When the client returns a RestartNeeded error, the strategy will try to reconnect
• One single task/thread is allowed to reconnect at a given moment
• While reconnecting, new requests will be pending until the reconnect finishes
• When the reconnect fails, all pending requests fails with the same error message
• When the reconnect succeed, all pending requests are processed

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Code review prechecks:

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Inline comments have been added for each method
• I have made corresponding changes to the documentation
• Code changes introduces no new problems or warnings
• Test cases have been added
• Dependent changes have been merged and published in downstream modules

[dvc94ch]

I don't have the bandwidth to do this PR justice. Looks good, although not sure why we need such a complicated solution. Sorry you're not getting enough appreciation for your work. I'll go ahead and approve...

[Lohann]

Yeah this PR is big and just look complex because of the number of third-part traits and adapters I had to implement:

Adapter	JsonRpsee Trait	Ethers Trait
EthClientAdapter	ClientT	JsonRpcClient
EthPubsubAdapter	SubscriptionT	PubsubClient
EthSubscription	Subscription	NotificationStream
EthError	Error	RpcError
EthRpcParams	ToRpcParams	Serialize

Our RPC client had to implement all those traits, this ended up bloating the code, besides that the actual reconnect logic is in the reconnect.rs and reconnect_impl.rs file, all the rest of the code are just implementation of those traits.