Expose rollup transaction statuses over sequencer RPC

[neysofu]

This PR introduces transaction status monitoring via JSON-RPC to sov-sequencer.

Transactions can have one of four statuses:

• Unknown.
• Submitted, i.e. accepted into the mempool.
• Published, i.e. published to the DA as part of a batch.
• Finalized, i.e. part of a finalized DA block.

The core status tracking logic is inside tx_status.rs, although the changes to lib.rs and batch_builder.rs are also meaningful.

I've also extended the client logic in util.rs to support the new subscription endpoints.

TODO

Finalized block notifications. Blocked by #1294.

Testing

One integration test over JSON-RPC and two unit tests. Resource deallocation after subscriptions are dropped is also tested.

[codecov]

Codecov Report

Attention: 17 lines in your changes are missing coverage. Please review.

Comparison is base (a8a234c) 78.9% compared to head (e067dbe) 79.4%.

❗ Current head e067dbe differs from pull request most recent head 9f5c667. Consider uploading reports for the commit 9f5c667 to get more accurate results

Additional details and impacted files

Files	Coverage Δ
full-node/sov-sequencer/src/tx_status.rs	100.0% <100.0%> (ø)
full-node/sov-sequencer/src/utils.rs	86.1% <100.0%> (+35.1%)	⬆️
...em/sov-modules-rollup-blueprint/src/runtime_rpc.rs	100.0% <100.0%> (ø)
rollup-interface/src/node/services/da.rs	0.0% <ø> (ø)
full-node/sov-sequencer/src/batch_builder.rs	97.1% <97.3%> (-0.1%)	⬇️
...ollup-interface/src/node/services/batch_builder.rs	0.0% <0.0%> (ø)
full-node/sov-sequencer/src/lib.rs	89.5% <86.9%> (-3.9%)	⬇️

... and 12 files with indirect coverage changes