feat: transaction reordering checks

[cdummett]

Summary

Rather than defaulting all markets to use reordering, PR switches fuzzing run to have at least one market with reordering enabled and one with reordering disabled for each product type (FUTR, FCAP, PERP, SPOT).

A new agent is added to check whether reordering is working correctly.

1. Agent submits an aggressive order
2. Agent submits a passive order

Continue sim execution and once both orders appear on the book, if...

• transaction reordering enabled, check aggressive order created after passive order (i.e. later block)
• transaction reordering disabled, check aggressive order created at same time as passive order (i.e. same block)

Fuzzing runs not capable of checking reordering of cancellations, passive transactions, and aggressive transactions as the sequence in which orders are executed within a block cannot be checked through APIs.