Mark reserved peers as explicit for gossipsub to avoid reputation decreasing

[xgreenx]

Closes #1384

After debugging the issue with transaction broadcasting in the Beta 4 network, I can confirm that it is related to the gossipsub reputation.

At some point, no one sends transactions to the authority node. When I manually restart one sentry node, this node starts to send transactions to the authority node. It sends transactions via gossiping and publishing:

• Publishing: I send a transaction to sentry 1, which sends it to authority.
• Gossiping: I send the transaction to sentry 0, it sends the transaction to sentry 1, and it sends the transaction to authority.

But at some point, gossiping doesn't work while publishing still works(Sentry 0 gossips transaction to Sentry 1, and Sentry 1 doesn't gossip it to authority).

After some time, the publishing doesn't work either.

The gossipsub has two thresholds, one for gossiping and one for publishing. We use these values:

So, the described behavior aligns with authority reputation decreasing. I don't know the reason why it happens(maybe decay), but adding all reserved peers to explicit peers should solve the problem.

[bvrooman]

In the production configuration, are the reserved nodes the sentry nodes? I.e., Is it the sentry nodes that are losing reputation when gossiping/publishing to the authority and eventually getting cut off?
Or is it your node that is getting cut off from the sentry nodes?