(cherrypick) Rollback unsuccessful preconfs in the mempool (#3264)

[MitchTurner]

cherrrypick #3264

Closes #3098.

When a block producer sends preconfirmation updates, sentry nodes optimistically treat the included transactions as committed, removing them from the mempool and marking their inputs as spent. If the producer crashes and re-produces a block at the same height without those transactions, the mempool is left in a stale state: inputs stay marked as spent and outputs linger in extracted_outputs, preventing re-submission of rolled-back transactions and causing dependents to reference non-existent UTXOs.

This PR makes preconfirmed transactions tentative until the canonical block at their height is imported. On import, preconfirmed txs present in the block are confirmed and their tracking is cleared; those absent are rolled back by restoring inputs, purging dependents, and emitting SqueezedOut notifications. It also adds integration tests: re-insertion after rollback, dependent eviction, normal confirmation, and stale-height cleanup.

• Breaking changes are clearly marked as such in the PR description and changelog

• New behavior is reflected in tests

• The specification matches the implemented behavior (link update PR if changes are needed)

• I have reviewed the code myself

• I have created follow-up issues caused by this PR and linked them here

Please go to the Preview tab and select the appropriate sub-template:

• Classic PR
• Bump version

[cursor]

PR Summary

Low Risk
Low risk: changes are limited to logging text and a changelog entry, with no functional txpool behavior modified.

Overview
Adds a .changes entry documenting rollback of stale preconfirmations.

In txpool_v2’s process_committed_transactions, simplifies/adjusts tracing::warn! messages for missing storage data (invariant-violation paths) without changing control flow.

^{Reviewed by Cursor Bugbot for commit 2413d4c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 78a204c. Configure here.}

[cursor]

Truncated log message ends with dangling "during."

Low Severity

The warning message "Storage data not found for the transaction during." is grammatically incomplete — "during" is a preposition left without an object. The original message referenced `remove_transaction` after "during", which was accidentally removed instead of being kept or the entire trailing clause being dropped.

 

^{Reviewed by Cursor Bugbot for commit 78a204c. Configure here.}