*: Update to next libp2p version 0.24.0

[mxinden]

For now here to test whether libp2p/rust-libp2p#1698 fixes paritytech/polkadot#1532.

Up until libp2p v0.24.0 is released this can serve as a place to collect necessary downstream changes.

Update libp2p to v0.24.0.

//CC @romanb @twittner @tomaka

[mxinden]

Looking at the various dashboards (CPU, memory, message count, ...) I can not tell a significant difference between nodes running 0.23 and 0.24 other than the connection count reduction through libp2p/rust-libp2p#1698.

kusama-sentry-ae1-0 and kusama-sentry-ae1-1 have been previously running with libp2p libp2p/rust-libp2p@e32ff74 and are running libp2p 0.24.0 since 2020-08-19 ~11 a.m. CEST.

kusama-sentry-ae1-0 runs with --enable-authority-discovery and thus makes excessive use of the DHT. The two nodes before yesterday 11 a.m. would never be on par in regards to connection count, but instead differ by ~100 connections, ignoring the periodic spikes triggered by authority discovery every 10 minutes. This is gone since libp2p 0.24.0.

Wild guess: Might this be related to libp2p/rust-libp2p#1710 which makes libp2p properly pass listen upgrade errors?

[tomaka]

You've probably forgotten to update a Cargo.toml somewhere. It seems that we're now using two different versions of libp2p at the same time.

[mxinden]

Good catch. I did a bad merge in 22cb019 not updating the libp2p version introduced in #4954.

[tomaka]

Please bot merge at your leisure.

[mxinden]

bot merge

[ghost]

Trying merge.