block_number_index added to callBundle reference type

[ciaranmcveigh5]

Motivation

Ability to quickly identify via an API call why a bundle did not land

paradigmxyz/reth#12353

Solution

Allow callBundle simulations to occur from a block index rather than a state_block_number, if a bundle has a target transaction that lands in block x this enables you to simulate from the exact index in block x where the target transaction landed to see if there were transactions higher in the block that caused a state conflict.

PR Checklist

• Ran cargo test --doc - no tests present for alloy_rpc_types_mev
• No documentation present on alloy_rpc_types_mev outside of "Types for the MEV bundle JSON-RPC namespace."

[ciaranmcveigh5]

One thing to note, there are 2 options naming wise, which likely have implications on the implementation

Don't have a strong opinion on which is better

Option 1

• Naming: block_number_index
• Fields that must be present: block_number & block_number_index

Option 2

• Naming: state_block_number_index
• Fields that must be present: block_number, state_block_number & state_block_number_index

This requires you to update the state_block_number to be the same as the block_number and include all 3 fields

[mattsse]

since this is just an extra setting, this should be fine

[ciaranmcveigh5]

Just updated the imports for TransactionIndex