Revert "chore: update libp2p to 0.52.1 (#14429)"

[altonen]

This reverts commit d38d176.

polkadot companion: paritytech/polkadot#7583
cumulus companion: paritytech/cumulus#2975

[dmitry-markin]

Is it required due to V1Lazy stuff?

[vstakhov]

I really don't like the sense of reverting updates, but it seems that 0.51 behaves more stable in terms of network connectivity (at least as we can see on Versi).

[altonen]

@dmitry-markin

It's due to DHT issues we're experiencing on Versi. I'll get back to this upgrade soon enough but in the mean time we have to revert because I don't know how long it's going to take to figure out the underlying issues and there are other important tasks as well.

[rphmeier]

This should be merged, no?

As far as we know, libp2p 0.52.1 is broken and should be taken out of master ASAP, right?

[altonen]

This should be merged, no?

As far as we know, libp2p 0.52.1 is broken and should be taken out of master ASAP, right?

yeah, just missing one last review from cumulus companion

[paritytech-cicd-pr]

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3397107

[bkchr]

bot merge force

[mxinden]

Let me know in case you need any help debugging the v0.52.1 issues you are seeing.

• Expanded on V1Lazy in Temporarily stop using V1Lazy #14691 (comment).
• Setting set_mode(Mode::Server) will revert to the previous Kademlia behavior, though as one would expect, disables the Kademlia client mode optimization.

[altonen]

@mxinden cheers, I'll be in contact with you when I start working the upgrade again and if I can't figure out the issues.