Handle account sequence correctly in bridge

[Raneet10]

Description

The job of the broadcaster component is, as the name suggests, to broadcast txs to tendermint. The ante handler is executed during checkTx (invoked by tendermint) and enforces some sanity checks on the tx sent (ensuring enough balance, correct signature, etc.) and at successful verification, increments the account sequence (akin to nonce).
If any of the checks were to fail, the appropriate error code is baked in sdk.TxResponse.

Currently, the broadcaster doesn't account for a failed sanity clause (and only checks for errors that pop up during the broadcast itself). This results in an incorrect increment of the bridge's "cached" account sequence and hence causes mismatch with the DB. This PR aims to fix this.

Changes

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)
• Changes only for a subset of nodes

Checklist

• I have added at least 2 reviewer or the whole pos-v1 team
• I have added sufficient documentation in code
• I will be resolving comments - if any - by pushing each fix in a separate commit and linking the commit hash in the comment reply

Testing

• I have added unit tests
• I have added tests to CI
• I have tested this code manually on local environment
• I have tested this code manually on remote devnet using express-cli
• I have tested this code manually on mumbai or amoy
• I have created new e2e tests into express-cli

[cffls]

LGTM! Thanks for adding the tests.