network: Update libp2p to 0.54.1

[nazar-pc]

Substrate currently uses libp2p 0.52.4 with lots of outdated dependencies, libp2p 0.53.0 was released 11 months ago and 0.54.0 was released 2 months ago in time for September's release cut.

This is way too slow, please consider upgrading libp2p to not lag behind for a year or more, this is bad for downstream users due to lots of duplicated and outdated dependencies, can also be problematic from security standpoint.

[bkchr]

CC @paritytech/networking

[lexnv]

It's definitely something we want to do!

I would wait a bit to update libp2p to the latest version:

• the amount of breaking changes from version to version is consuming a lot of resources (I gave up after half a day of hacking at the new API to get it just to compile).
• we need a better process for catching regressions in networking backend updates. Last time we updated, we discovered a few weeks later a CPU regression of around 20-30%. Here is a good document written by @AndreiEres https://hackmd.io/@AndreiEres/networking-bench (and Benchmark network stack CPU usage  #5220) with a path forward.
• Ideally this could happen after Litep2p stabilizes. We'd need a safe fallback for unexpected issues, and the version prior to 0.52.4 started to manifest panics for nodes running for 5-6 days 🙈

After we update libp2p to latest version, we could start looking at performance issues: #5221

[nazar-pc]

We jump onto latest version of libp2p at https://github.com/autonomys/subspace fairly quickly and while I agree it is annoying to do all the changes needed to migrate to new version, it typically takes me a couple of hours to do. And I am yet to see show-stopping issues after upgrade itself (though we do not have as robust testing and benchmarking capabilities yet).

I can probably do this upgrade for you (in two steps: first to 0.53.x and then to 0.54.x to make review easier), but it takes you guys a really long time to review with regular merge conflicts in between (I have 4 PRs that I opened that are waiting for review for over a week each, some are waiting for way longer than a week), so while I understand you probably have good reasons for this, it is a big investment.

Let me know if you're willing to commit to timely review and I'll take a look at doing this in the near future myself, it isn't a big deal.

Substrate is a large source of outdated dependencies that triggered RUSTSEC alerts in the past already as well as causing other issues, like pulling old version of libp2p-quic (seems impossible to disable right now) that pulls old version of ring that fails to compile on some platforms, all for dependency we don't even use in the runtime.

[lexnv]

@nazar-pc We would love to get some help on this if you have some extra bandwidth! 🙏

I'll have a pass soon for the remaining networking PRs, thanks for contributing again!

[nazar-pc]

Noted, I'll update once I get to it

[nazar-pc]

0.53.2 is done here: #6248

Please assign this issue to me, I'll take care of the rest too.

UPD: 0.54.1 is also there, it was too easy to do to delay it further.