fix(p2p): adaptive chain exchange timeout

[hanabi1224]

Summary of changes

This PR tries to address the below comment on CHAIN_EXCHANGE_TIMEOUT

/// Timeout for response from an RPC request
// This value could be tweaked, this is just set pretty low to avoid peers
// timing out requests from slowing the node down. If increase, should create a
// countermeasure for this.

Changes introduced in this pull request:

• introduce AdaptiveValueProvider to automatically adjust CHAIN_EXCHANGE_TIMEOUT on successes and failures

https://github.com/ChainSafe/forest/actions/runs/9754275564/job/26921065275?pr=4470#step:8:445

2024-07-02T03:11:08.618161Z  INFO forest_filecoin::chain_sync::network_context: Decreased chain exchange timeout to 2500ms. Current average: 96ms
2024-07-02T03:11:08.659245Z  INFO forest_filecoin::chain_sync::network_context: Decreased chain exchange timeout to 2000ms. Current average: 39ms

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[LesnyRumcajs]

Could we abstract it to a higher level class to avoid having this lower-level logic in such places?

[hanabi1224]

Does this crate look like a good fit? https://crates.io/crates/incr_stats

[LesnyRumcajs]

I'd avoid relying on niche crates, since it should be simple to implement a basic abstraction ourselves. Niche crates bloat dependency tree and are more susceptible to malicious code (since there's hardly anyone reviewing the changes).

[hanabi1224]

Fixed.

[hanabi1224]

@lemmih @LesnyRumcajs can you please re-approve? Thanks!