Update to go-libp2p 0.22

[BigLep]

Done Criteria

Kubo successfully builds and tests pass with go-libp2p 0.22

Why Important

1. Validate the go-libp2p 0.22 release to increase our confidence in having other groups upgrading to it. Kubo updating forces go-libp2p to bubble up the breaking changes through a large part of our stack, which makes sure that other users of our stack won’t run into the same problems.
2. General maintenance so we have good operational posture. We want to be able to consume go-libp2p updates quickly so that if there is a bug fix or new feature, we can adopt it quick. We know the 0.22 release introduces more work, and we want to get it behind us so we don't absorb the work at an inoportune time.

Notes

1. Enabling resource management by default is a separate workstream (Integrate/expose go-libp2p resource manager #8761 ) and shouldn't be conflated with this.

[BigLep]

2022-09-01 conversation: @ajnavarro and @Jorropo will have a call about how to handle FX challenges with the libp2p changes with callbacks.

[Jorropo]

Related: ipfs/go-bitswap#580