Upgrade libp2p from 0.51.1

[LesnyRumcajs]

Issue summary
The recent upgrade #2732 most likely introduced a regression #2755

Reverting this upgrade seems to mitigate the issue (all my mainnet sync trials passed for Forest pinned to 0.51.1, whereas none passed with the updated libp2p). That was around ten trials.

The revert #2759 is a temporary workaround, the library should be updated, and the deprecated suppressions should be removed. These can be found by gripping this ticket link in the codebase.

⚠️ when updating libp2p, make sure it syncs to mainnet.

If it turns out that the issue is back again without the libp2p update, this one should be closed and the original bug ticket should get re-opened.

Other information and links

[LesnyRumcajs]

revertio again #3219

[thomaseizinger]

Let us (@mxinden & myself) know if we can help you with the update! :)

[LesnyRumcajs]

@thomaseizinger Thanks! I really appreciate it, I will reach out once I contrive a minimal reproducible example of the issue.

[hanabi1224]

Update: the issue is likely to be related to libp2p/rust-libp2p#4250 @LesnyRumcajs has forest running well by raising the connection limit

[LesnyRumcajs]

There were some other changes that may have helped, e.g., not banning peers when they abruptly close the connection.

[LesnyRumcajs]

Closed via #3267