libp2p v3 release issue

[achingbrain]

This is a tracking issue for items that will cause v3 of libp2p to be released. The idea is to only do this once per year - v2 shipped in early September 2024 so we are approaching a reasonable window to release v3.

This list is currently non-exhaustive and may grow and/or shrink over time.

• Remove all @deprecated methods and fields from packages in this monorepo - fix!: remove deprecated code #3271
• Remove all @deprecated methods and fields from @multiformats/multiaddr - fix!: simplify API multiformats/js-multiaddr#427
• Remove @libp2p/pubsub and pubsub interface compliance tests
• Switch await from async iterables to web streams? feat!: muxed streams as web streams #1847 A deal breaker: feat!: muxed streams as web streams #1847 (comment)
• Streams as EventTargets #3226 / feat!: streams as EventTargets #3218
• Update to @multiformats/multiaddr v13.x.x - deps!: update @multiformats/multiaddr to 13.x.x #3268
• Remove Upgrader dependency from transports
• Address flakiness in transport interop tests
• Async middleware - feat: async middleware #3204
• Migration guide
• Blog post

Post v3 release tasks

• Upgrade @chainsafe/libp2p-yamux to EventTarget streams
• Upgrade @chainsafe/libp2p-noise to EventTarget streams
• Upgrade @chainsafe/libp2p-gossipsub to EventTarget streams
• Upgrade @chainsafe/libp2p-quic to EventTarget streams
• Add quic back to transport interop tests
• Re-enable gossipsub/hybrid interop tests

[p-shahi]

Part of ipshipyard/roadmaps#22