feat: remove peers after several unsuccessful attempts

[mattsse]

supersedes #3076

we're tracking what kind of error caused a failed dial/disconnect. if the error is severe, for example connection refused we backoff in and increase a counter.

previously peers, even offline peers weren't cleared from the peerset, but backed off with increasing duration.

this adds a new config threshold after which peers are removed from the set, for example if a peer is not reachable after the 5th attempt, it is removed from the set

[codecov]

Codecov Report

Merging #3780 (10c28bd) into main (e3ac77a) will increase coverage by 8.32%.
The diff coverage is 85.07%.

Impacted Files	Coverage Δ
crates/net/network/src/error.rs	76.04% <50.00%> (+16.04%)	⬆️
crates/net/network/src/peers/manager.rs	83.82% <85.93%> (+8.13%)	⬆️
crates/config/src/config.rs	64.65% <100.00%> (ø)

... and 189 files with indirect coverage changes

Flag	Coverage Δ
integration-tests	12.73% <14.92%> (-3.06%)	⬇️
unit-tests	64.31% <85.07%> (+10.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
reth binary	26.15% <100.00%> (+1.41%)	⬆️
blockchain tree	83.02% <ø> (+41.29%)	⬆️
pipeline	87.13% <ø> (+7.89%)	⬆️
storage (db)	73.27% <ø> (+14.10%)	⬆️
trie	94.65% <ø> (+23.06%)	⬆️
txpool	48.76% <ø> (+4.69%)	⬆️
networking	77.33% <84.84%> (+8.73%)	⬆️
rpc	49.94% <ø> (-1.47%)	⬇️
consensus	64.90% <ø> (+8.10%)	⬆️
revm	32.94% <ø> (+4.26%)	⬆️
payload builder	4.13% <ø> (-2.49%)	⬇️
primitives	87.99% <ø> (+9.66%)	⬆️

[Rjected]

this seems reasonable for removing offline or otherwise misbehaving peers from the peerset, lgtm