Gossip + Memberlist sync

[rogeralsing]

In some cases, e.g. using SeedNodeProvider, we might be too eager to start sending gossip requests.
e.g.
Node A tells Node C that Node B exists
Node C, now has node B in its memberlist, and immediately starts sending gossip

This is fine, but node C and node B might not yet have established a remote connection. and the gossip might timeout due to this.

not a major issue, but results in needless excessive logging

[rogeralsing]

Various solutions could be interesting here.
e.g. memberlist could know how long it has known about other members. and gossip could be told to not gossip to nodes that are younger than x seconds.

or memberlist could have knowledge on the remote status of each member. e.g. know if we are connected to this node yet