feat: bump revm to 21.0.0 and alloy to 0.13.0

[klkvr]

Motivation

Bumps revm to latest version. I've removed CfgEnv from BlockchainDbMeta as it seems unused and it's now generic over SpecId which we ideally don't need to deal with on fork-db lavel.

Solution

PR Checklist

• Fixed Tests
• Added Documentation
• Breaking changes

[zerosnacks]

Marked this as ready for review, please move back to draft @klkvr if this is incorrect

[jenpaff]

@zerosnacks can you confirm that this will only be merged once we're done with #44 ?

[zerosnacks]

It likely makes sense to merge once #44 is in a mergeable state as that will test the changes

That said, the scope is minimal enough that is could be merged prior if it is a blocker for anything

[jenpaff]

It likely makes sense to merge once #44 is in a mergeable state as that will test the changes

That said, the scope is minimal enough that is could be merged prior if it is a blocker for anything

Not blocking, just wanted to get an idea since it was open & approved for a while now. Marking as blocked & we can decide when to merge

[klkvr]

hmm, didn't realize we have this serde breaking change. @rakita @mattsse should we fix it?

[klkvr]

or I guess this shouldn't really affect anything

[rakita]

hm this is a change from U256 to u128 fields. I didn't get any complaints on this part, would say it is fine to leave as is