feat: Add other state used to ConflictFinder

[bertmiller]

The job of the conflict finder is to identify potential conflicting orders. Currently it does this by looking at storage read and write overlaps. We need to add the other possible state access patterns too. Luckily we already have these in the UsedStateTrace but they need to be reflected in the ConflictFinder.

Also, we should add nonces to this.

[grasphoper]

Hi @bertmiller, can I take this?

[grasphoper]

I've taken a look at the code and other possible conflicts to add. They are:

• read_balances can conflict with sent_amount, received_amount
• read_slot, write_slot can conflict with destructed_contracts
• destructed_contracts can conflict with each other
• created_contracts can conflict with each other

Do we want to add all of these? And did you have any other combinations in mind?

As for the nonces, they seem to be partially taken care of already, as they're recorded as read_slot + write_slot for EOA at 0th slot here. There's a corner case though: right now, if we have 2 TXs that are using different nonces for the same EOA, we deem them "conflicting", which should not be the case. Not obvious how to work around this yet (other than changing how the nonce usage is recorded into the UsedStateTrace)