Upgrade `gossipsub` to v1.1

[ralexstokes]

Spec: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/README.md

Ref. impl.: https://github.com/libp2p/go-libp2p-pubsub

[ralexstokes]

v1.1 spec: https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md

[mystical-prog]

@pacrob I will like to work on this issue and make PRs on pragmatic basis

[mystical-prog]

I have broken down the entire upgrade process into multiple steps -

• Direct Peers
• Peer Exchange & Prune Back Off
• Activation Function
• Peer Scoring

Direct Peers PR has been merged and currently I am working towards Peer Exchange & Prune Back Off, while going through the go-libp2p implementation I have found that py-libp2p doesn't have CertifiedAddrBook implementation in PeerStore.

[seetadev]

@mystical-prog : Hi Vraj. That’s excellent progress — great to see how methodically you’ve broken down the Gossipsub upgrade into actionable steps.

Splitting the work across Direct Peers, Peer Exchange & Prune Back Off, Activation Function, and Peer Scoring is a wonderful approach and will make the implementation far more manageable and robust.

Great work on Direct Peers — that’s a big milestone! 🎉

Very nice to hear you're already deep into the Peer Exchange & Prune Back Off project modules. Your observation around the missing CertifiedAddrBook in py-libp2p’s PeerStore is spot-on — identifying those gaps early is crucial for aligning closer with the go-libp2p reference.

We highly appreciate the careful cross-referencing you’re doing with the go-libp2p implementation. Your attention to detail and steady momentum are making a big impact on strengthening the py-libp2p stack 🚀

On the same note, thank you for opening up the issue on CertifiedAddrBook: #638
Appreciate your initiative :)

[seetadev]

@mystical-prog : Hi Vraj.

Wish to also share to keep in sync with Gossipsub interop efforts, which are nearing production at libp2p/test-plans#648. Please also visit https://github.com/ppopth/pubsub-shadow/tree/main .