Dont rely on feature unification

[MartinquaXD]

Description

Follow up to #4238.
While that PR correctly identified the issue that https was not enabled when is should have been it did not resolve it correctly. It incorrectly added the tls feature on the workspace toml assuming this will cause the feature to always be enabled but that's actually not correct.
The driver still did not support https. I was able to reproduce that by copying the new test_https unit test to the driver main and running it from there.
cargo test -- test_https passed while cargo test -p driver -- test_https did not. This indicates that https support was only enabled when the whole workspace gets compiled as one. When we only compiled the driver feature unification was not there to pull in the necessary features.

This PR addresses this by explicitly enabling all the necessary features such that every crate can be compiled and tested individually without complaints.

Changes

Add a bunch of features that were previously assumed to not be needed because feature unification pulled them in without our knowledge.

Since alloy likes to follow the pattern of using feature flags to enable compilation of sub-crates I avoided the use of feature flags by depending on the underlying sub-crate whenever possible. For example this caused me to introduce alloy_rpc_types_eth and alloy_rpc_types_trace on the workspace level.

This PR only fixes the symptom but doesn't prevent us from relying on feature unification without our knowledge again. This should be addressed in a follow up PR.

How to test

After that was done I repeated the test with cargo -p driver -- test_https and it passed. Indicating that the ethrpc crate now correctly causes https to be supported in any crate that depends on it.

[m-sz]

LGTM

[gemini-code-assist]

Code Review

This pull request addresses an issue with Cargo's feature unification by making crate dependencies and their features explicit in each Cargo.toml. This ensures each crate can be built and tested independently. The changes involve adding specific features to alloy and other dependencies across multiple crates, and updating use statements accordingly. No critical issues were found in this implementation.