test: add a test showing that an initiator can eventually connect when the responder is started

[etorreborre]

The PR makes sure that we can connect to an upstream node if:

• It is not yet started when we start.
• It is restarted while we are connected.

In order to do this:

• The reading/writing stages in the Muxer are supervised.
• The Muxer itself is supervised by the Connection which closes the loop since the Connection is supervised by the Manager.
• FetchBlock errors are not considered as fatal anymore since they can happen on disconnection.
• Similarly a rollback can fail on reconnection if the corresponding block was not yet downloaded
  -> TODO: what guarantees that we will eventually download the block?

In addition:

• Two tests were added to support the 2 disconnection scenarii presented earlier.
• The tests were refactored since the setup and the assertions contains more code now.
• The Muxer has a role field that is used to annotate traces, which is useful when reading log messages.
• The connection timeout that was hard-coded in the Manager is now part of its configuration.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[etorreborre]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.