Consider updating web3 crate

[sergeyboyko0791]

I tried to update web3 crate to use its web3::transport::Eip1193 as we discussed #1551 (comment)

I seem to update the dependencies correctly by forking parity-ethereum repo.
But then I faced too many compilation errors that should be handled on our side. They are mostly due to the changed relationship between ethereum-types, rlp and web3 crates.
Errors: https://gist.github.com/sergeyboyko0791/b3d1f2b4736ae98c3434bd76deb0db3e

I think that the effort to update the web3 crate doesn't worth it taking also into account that web3::transport::Eip1193 should be wrapped into a Send + Sync structure (using event-driven pattern).

cc: @artemii235

[sergeyboyko0791]

A dev state (not to forget): c87e84c

[sergeyboyko0791]

I faced a problem when tried to send RPC requests using an out-of-dated web3 crate: they used an old ethereum_types::U256 type that requires the number to start with 0x prefix on deserialization, but MetaMask RPC sometimes returns without the prefix.

So I decided to finish updating web3 crate. What I've gotten: 476e53c

[dimxy]

There is a statement in the web3 client that we use https://crates.io/crates/web3 that it is not actively maintained and for new projects it is recommended to use another client: https://github.com/gakonst/ethers-rs. Maybe we should consider changing it too

[dimxy]

https://github.com/gakonst/ethers-rs is being deprecated too.
This is the alternative https://github.com/alloy-rs/alloy
and this https://github.com/foundry-rs/foundry