Explicit peers

[mempirate]

Issue Addressed

Closes #5268

Proposed Changes

This PR implements explicit peering agreements (https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#explicit-peering-agreements). It was decided not to add a separate --explicit-peers flag, but instead instantiate trusted peers as explicit. This means that when a trusted peer is defined, it will have the following properties:

• exempt from peer scoring
• automatic reconnects
• unconditional forwarding of all messages

[CLAassistant]

All committers have signed the CLA.

[AgeManning]

@mempirate - Thanks for the PR.

You've caught us at a time where we are actively going through and removing old/deprecated and non-critical CLI flags, as we've had a few complaints of there being too many.

How do you feel about just using the trusted-peers CLI flag. i.e all trusted peers become explicit peers on the gossipsub level. I think this what should have been implemented when we added the trusted-peers flag.

[mempirate]

@AgeManning I think that also makes sense as an approach! Agreed that there's a lot of overlapping functionality.

Done in following commit.

[AgeManning]

Nice thanks for the addition!

Also, in the future, we can always change the base of the PR, no need to make a new one :)

(I know this, because I accidentally do it all the time 😅 )

[pawanjay176]

@Mergifyio queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The pull request conflicts with at least one pull request ahead in queue.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[pawanjay176]

@Mergifyio queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The pull request #5333 has been manually updated.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[paulhauner]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 641f6be