feat(code): Implement Solution 1 for the RoundSync

[ancazamfir]

Closes: #XXX
From the Round sync spec:

Solution 1 (similar to what we have now and what StarkWare implements)

• upon entering the round r process broadcast the certificate EnterRoundCertificate (in round=0 this certificate is nil so a process doesn’t broadcast it) and reset lastPrevote and lastPrecommit
• upon sending PREVOTE message a process trigger timeoutRebroadcastPrevote
  • If timeout timeoutRebroadcastPrevote expires before process triggers timeoutPrevote or send a PRECOMMIT message, a process call REBROADCAST() and starts timeoutRebroadcastPrevote again
• upon sending PRECOMMIT message a process cancels existing timeoutRebroadcastPrevote and starts timeoutRebroadcastPrecommit
  • If timeout timeoutRebroadcastPrecommit expires before process triggers timeoutPrecommit or receives a roundCertificate for a new round, a process call REBROADCAST() and starts timeoutRebroadcastPrecommit again
• upon receiving a round certificate for a new round process cancel any existing timeouts
• Timeouts can be set:
• timeoutRebroadcastPrevote(r) = timeoutPrevote(r) and
• timeoutRebroadcastPrecommit(r) = timeoutPrecommit(r)

REBROADCAST() - broadcasts the current non-nil values of EnterRoundCertificate, lastPrevote and lastPrecommit

Summary of the changes compared with parent branch:

• bring back the two timers TimeoutKind::PrevoteRebroadcast, TimeoutKind::PrecommitRebroadcast
• cancel the PrevoteRebroadcast timer when a precommit is sent
• cancel the PrevoteRebroadcast timer when the Prevote timer is started
• cancel the PrecommitRebroadcast timer when the Precommit timer is started
• cancel the rebroadcast timers when a round certificate is received
  • Note: Should add check that the certificate is a well formed PrecommitAny or SkipRound type (with correct voting power) and not cancel timers if not (cc @nenadmilosevic95)

The rest of the points in Solution 1 are included in parent branch.

---

PR author checklist

For all contributors

• Reference a GitHub issue
• Ensure the PR title follows the conventional commits spec
• Add a release note in RELEASE_NOTES.md if the change warrants it
• Add an entry in BREAKING_CHANGES.md if the change warrants it

For external contributors

• Maintainers of Malachite are allowed to push changes to the branch

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (acc180b) to head (259369d).
Report is 4 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@     Coverage Diff      @@
##   main   #1033   +/-   ##
============================
============================

[nenadmilosevic95]

LGTM, I left some comments!

[romac]

I guess we can close this now, right?

[faddat]

@romac is that because of the recently-merged networking code, or something else?

Just interested in what makes this pr closable.

[romac]

@romac is that because of the recently-merged networking code, or something else?

Just interested in what makes this pr closable.

It is because the other solution we had mind was merged instead: #1032