[BCFR-1048] - Logic to solve ocassional nonce gap issues

[Farber98]

Description:

• Change the getSequenceForAddr function to use NonceAt instead of PendingNonceAt.
• We use the mined transaction count (SequenceAt) to determine the next nonce to use instead of the pending transaction count (PendingSequenceAt). This allows the TXM to broadcast and track transactions for nonces starting from the last mined transaction preventing the perpetuation of a potential nonce gap.
• Consideration: Any transactions already in the mempool would be attempted to be overwritten but an older transaction can get included before being overwritten. Such could be the case if there was a nonce gap that gets filled unblocking the transactions. If that occurs, there could be short term noise in the logs surfacing that a transaction expired without ever getting a receipt.

Steps a NOP should follow to handle nonce gap issue:

• disable NonceAutoSync
• mark abandon all current transactions checkbox

Resources

• Ticket
• Discussion

Merge together with:

• [BCFR-963] - Remove Nonce Manual Override setting from UI operator-ui#89

[github-actions]

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube