txmgr: Queue.Send() uses q.txMgr.SendAsync

[geoknee]

This should ensure that transactions are confirmed on chain in the order Queue.Send() is called, without sacrificing parallel tx submission.

Description

Updates the txMgr Queue.Send() entrypoint to use txMgr.SendAsync()

Tests

See #13124

Additional context

Since Holocene, the order of batches landing on chain must be strictly adhered to. The batcher has been hardened to keep batches ordered before they get to the txMgr, but the txMgr fails to preserve the order of txs that the batcher sends to it. This caused a safe head stall on Base Sepolia.

The changes here also affect op-challenger.

Metadata

Fixes #12947

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.74%. Comparing base (72eb311) to head (8c06a80).
Report is 12 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #13120      +/-   ##
===========================================
- Coverage    44.46%   42.74%   -1.73%     
===========================================
  Files          798      742      -56     
  Lines        71682    67028    -4654     
===========================================
- Hits         31874    28648    -3226     
+ Misses       37224    35977    -1247     
+ Partials      2584     2403     -181     

Flag	Coverage Δ
cannon-go-tests-32	?
cannon-go-tests-64	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
op-service/txmgr/queue.go	82.75% <100.00%> (+4.03%)	⬆️

... and 63 files with indirect coverage changes

[clabby]

The changes here also affect op-challenger.

I think this change is fine for op-challenger, but will defer to @ajsutton