Revert "chore: update go-libp2p"

[dirkmc]

This reverts commit f7fbaef.

When attempting to do a storage deal against our miner running the latest master, we would see the following error whenever graphsync received a block on the miner:

2021-05-20T19:16:33.361+0300    DEBUG   graphsync_network       network/libp2p_impl.go:149      graphsync net handleNewStream from 12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS
2021-05-20T19:16:33.361+0300    DEBUG   graphsync       responsecache/responsecache.go:75       Received block from network: bafykbzacecwiyfre32qd747cmg6frj5vhvqr6xffwgllvssy75lxab4ncrvnw
2021-05-20T19:16:33.361+0300    DEBUG   graphsync       responsecache/responsecache.go:81       Traverse link bafykbzacecwiyfre32qd747cmg6frj5vhvqr6xffwgllvssy75lxab4ncrvnw on request ID 4
2021-05-20T19:16:33.369+0300    DEBUG   markets loggers/loggers.go:35   data transfer event     {"name": "DataReceivedProgress", "status": "Ongoing", "transfer ID": 1621517646811668388, "channel ID": "12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS-12D3KooWQrZnhRaBecSZYKR815zH65xkg1TvfyPWUGYwehHvVEKB-1621517646811668388", "sent": 0, "received": 30431, "queued": 0, "received count": 1, "total size": 0, "remote peer": "12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS", "event message": "", "channel message": ""}
2021-05-20T19:16:33.374+0300    DEBUG   markets loggers/loggers.go:35   data transfer event     {"name": "DataReceived", "status": "Ongoing", "transfer ID": 1621517646811668388, "channel ID": "12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS-12D3KooWQrZnhRaBecSZYKR815zH65xkg1TvfyPWUGYwehHvVEKB-1621517646811668388", "sent": 0, "received": 30431, "queued": 0, "received count": 1, "total size": 0, "remote peer": "12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS", "event message": "", "channel message": ""}
2021-05-20T19:16:33.538+0300    DEBUG   graphsync_network       network/libp2p_impl.go:143      graphsync net handleNewStream from 12D3KooWHMGTcNbS64arHyaPoUv6NrZi9V63kuVbnE6jbBjm5EUS error: stream reset

After reverting this commit, the problem goes away and the data transfer completes successfully.