feat(bridge-withdrawer): Bridge withdrawer transaction submission

[itamarreif]

Summary

This adds the Submitter and merges in the Watcher related logic into a single WithdrawService.

Submitter receives batches of rollup transactions that have been converted into sequencer Actions from the Batcher and does the following:

1. fetch the current nonce and create the UnsignedTransaction
2. sign the transaction
3. broadcast_tx_commit

If submission to the sequencer fails for any reason (either in CheckTx or DeliverTx), the Submitter will stop, instead relying on the service's recovery process to reconstruct the batch from rollup transaction and resubmit.

Background

Withdrawal batches need to be submitted to the sequencer.

Changes

• Add Submitter
• Add logic for converting the events reaped from rollup to Actions
• a lot of random cleanup

Testing

How are these changes tested?

Metrics

• Some metrics we use in composer already since i copied over a good amount of submission logic:
  • NONCE_FETCH_COUNT
  • NONCE_FETCH_FAILURE_COUNT
  • NONCE_FETCH_LATENCY
  • CURRENT_NONCE
  • SEQUENCER_SUBMISSION_FAILURE_COUNT
  • SEQUENCER_SUBMISSION_LATENCY

Related Issues

Link any issues that are related, prefer full github links.

closes

[noot]

the event.sender is an evm address - we need to parse the event.memo to get the destination sequencer address (or check if it's an ics20withdrawal)

also thinking amount needs a "precision" as well, as going to the evm for example we multiply by some precision so here we'd need to divide by that precision

memo should also be updated to store the evm block number and tx hash

[noot]

i propose the evm tx memo looks like:

{
    "astria": {
         "recipient_address": "astriaaddress",
    },
    "forward": {
         "receiver": "destinationchainbech32address",
         "port": "transfer",
         "channel": "channel-123"
    }
} 

where forward is set only if this is an ics20 withdrawal, and astria can be unset. if it's a withdrawal to a sequencer account, then astria is set and forward is unset

[noot]

i also propose the memo for BridgeUnlockAction looks like

{
     "rollup_block_number": 99,
     "rollup_tx_hash": "tx_hash"
}

tx_hash comes from event_with_metadata.

[noot]

no more evm tx memo for withdrawals to sequencer, see #1101

for ibc withdrawals, channel/port are hardcoded. the ibc packet memo should contain whatever is in the Ics20Withdrawal event memo plus additional data:

{
     "rollup_block_number": 99,
     "rollup_tx_hash": "tx_hash",
     "rollup_sender_address": "0x..."
}

[noot]

mostly looks good, my main concerns before merging:

• fetching chain id from sequencer instead of config
• fetching fee asset id from sequencer or setting in config instead of hardcoding
• conversion of event into action needs to be updated