chore(primitives): replace HashMap re-exports with alloy_primitives::map

[DaniPopes]

The semantics of the "hashbrown" feature are the same, meaning that enabling it overrides std with hashbrown, as well as it being the default if std is not enabled.

See: alloy-rs/core#743

[rakita]

I would remove alloy-primitives/default to leave std map as a default. Other hashers could be enabled by alloy-primitives features

[DaniPopes]

Sure, do you want to expose these features in revm too?

[DaniPopes]

A small problem with this is that some methods only work with the std hasher (new, with_capacity, From::from...), which is fine if it's the default, but if you change hasher revm will fail to compile and it might not be caught in CI

[rakita]

Was surprised by new, From::from when I looked at the changes. We should have CI that switches to non standard hasher.

I want to experiment with this a little, features get unified if same version of dependency is included, as in include both revm and revm-primitives, so we could by enabling revm-primitives features enable them inside revm.

Need to check what happens if versions are not same, and how brittle is this pattern.

You don't need to do it now in this PR, but I will maybe add it later when I come to this.

[rakita]

Read on this: https://doc.rust-lang.org/cargo/reference/features.html#feature-unification

[rakita]

lgtm, merging this first to not have conflict later.

Default hasher in primitives was put to std.