fix(prelude): enable rpc-client exports, enable pubsub on provider and add missing exports from alloy/core

[zerosnacks]

Motivation

Related to #391, has a mirror PR for alloy/examples here: alloy-rs/examples#37

Solution

• Enables the pubsub feature on alloy-provider when using provider-ws or provider-ipc
• Exports rpc-client-http-reqwest, rpc-client-http-hyper, rpc-client-ws, rpc-client-ipc as feature flags. It possibly makes sense to add a rpc-client-pubsub feature flag but I did not see an immediate reason.

Additive:

• Added missing native-keccak flag that was not re-exported from alloy/core.

This PR is intended to be non-breaking.

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[zerosnacks]

I noticed the alloy/serde crate is currently not exported in alloy. Is this something we would want @prestwich? It would be useful for the create_instances example in alloy/examples as it currently does not implement a case showing the use of ethers-rs equivalent of serde_helpers::Numeric.

https://github.com/alloy-rs/examples/blob/main/examples/big-numbers/examples/create_instances.rs

vs

https://github.com/gakonst/ethers-rs/blob/master/examples/big-numbers/examples/create_instances.rs

[prestwich]

It should be included for the benefit of people implementing their own network types

[zerosnacks]

It should be included for the benefit of people implementing their own network types

Makes sense, I've decided to split up #391 into two parts, one with non-breaking changes with relatively high priority (this PR) and a follow up more major PR that would include a larger refactor, additional exports (like serde) with proposed breaking changes and will likely requires some further discussion (see #391).

I'm moving this out of draft again so it can be reviewed and downstream tickets can become unblocked.

[zerosnacks]

Closing this in favor of PR #421 that handles the refactor as more issues have popped up and the impact of (if any) breaking changes appears to be small.