Improve latency handling

[ghost]

Description

Improve latency handling to make the system more resilient

Fixes #498 #497 #499

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

To test with high latency, we can use a tool like comcast and with some latencies:

comcast --device=lo0 --latency=200 --target-bw=1000 --packet-loss=10%

• We should not have timeouts in the ReplicateTransactionChain
• We should not have timeouts in the self-repair

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[apoorv-2204]

archethic-node/lib/archethic/mining/distributed_workflow.ex

Line 351 in 4507fb8

# TODO: Provide a better waiting time management

we can also leverage this, as Mentioned by Samuel.

# TODO: Provide a better waiting time management
          # for example rolling percentile latency could be way to achieve this
          # (https://cs.stackexchange.com/a/129178)

[prix-uniris]

A better way for import can be like this syntax : alias MODULE.{ModuleName1, ModuleName2, etc.}.
https://elixir-lang.org/getting-started/alias-require-and-import.html#multi-aliasimportrequireuse

[ghost]

I think this can be improved for the entire codebase, so the scope of the PR would be too big I guess.
But yes you are right, it might be better.

[prix-uniris]

Few typos and improvements can be made.

[prix-uniris]

Tested with comcast with 2 nodes locally, worked fine.
comcast --device=lo --latency=200 --target-bw=1000 --packet-loss=10%
LGTM