[WIP]fix: retry block broadcast and proposal

[deffrian]

Ref: A-453

[AztecBot]

Flakey Tests

🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/d97198198f6be2f5�d97198198f6be2f58;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_p2p/rediscovery.test.ts (178s) (code: 1) group:e2e-p2p-epoch-flakes (\033Nikita Meshcheriakov\033: fix: retry block broadcast and proposal)
\033FLAKED\033 (8;;http://ci.aztec-labs.com/f41fda0730f2031b�f41fda0730f2031b8;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_l1_reorgs.test.ts (386s) (code: 1) group:e2e-p2p-epoch-flakes (\033Nikita Meshcheriakov\033: fix: retry block broadcast and proposal)

[spalladino]

I think retrying some operations during block building is good if we think they could fail, but I don't think this addresses the main issue, which is an unhandled exception during building a block. Still, before we jump into implementing, we need to make a good pass at understanding what steps can fail, define what we want to roll back to, and then implement. For instance, what do we want to do if building the block fails? Or if the sequencer publisher fails?

Let's talk over standup about this!

[spalladino]

Hah, good catch! Can you push this in a separate PR?

[spalladino]

Also, implementation wise, it's better if you can leverage one of the retry or retryUntil functions in foundation, so we don't need so much code for the retries.