state machine updates for tx replay

[hstove]

• Closes Tx Replay: Signer detects forks and updates state machine with replay transactions #5968

This PR implements:

• Detecting forks in the signer state machine
• Updating the tenure fork info API to include dropped blocks, which can be used to construct the tx replay set
• Include a Vec<StacksTransaction> in state machine updates
  • For now, this vec is cleared as soon as a new Stacks block comes in (regardless of that block's contents). This allows us to monitor state machine updates

This builds on top of #6048 (which we should merge first)

[hstove]

Current state of this PR:

• tx_replay_set, an Option<Vec<StacksTransaction>>, is added the SignerStateMachine
• signer_state detects a bitcoin fork in bitcoin_block_arrival and fetches dropped blocks
• The "fork info" API is updated to included dropped Nakamoto blocks
• The signer updates their local signer state machine with the dropped tx's from this API
• A new integration test triggers a Bitcoin fork and asserts that the state machine has the right tx replay set

[hstove]

I've updated this PR with an additional test scenario that tests forked txs across multiple tenures, which caught an issue regarding the order of the replay set

[kantai]

This LGTM, just a few comments

[hstove]

All comments addressed, plz re-review!

[obycode]

LGTM!

[hstove]

Fixed a conflict, re-requesting reviews 🙏