feat: improve UsedStateEVMInspector by adding other op-codes that read or write

During simulation we use an EVM inspector to get state that is used by a transaction by looking at the storage slots that a transaction reads and writes from. We could supplement this by adding other op-codes that read or write state. A few off the top of my head that we should add:

• balance
• selfbalance
• create (balance and nonce is read)
• create2 (balance and nonce is read)
• selfdestruct (balance and nonce is read)

Do we need to support EXTCODECOPY, EXTCODEHASH, or EXTCODESIZE too? Not sure but I think so because some transactions might condition their execution on these and others might deploy contracts.

The goal would be to improve our coverage of what state is being used and how.

https://github.com/flashbots/rbuilder/blob/develop/crates/rbuilder/src/building/evm_inspector.rs