More lenient ipv6 auto-update

[AgeManning]

Description

On IPv4 dominated networks, local routing tables can be fully populated with ipv4 nodes limiting the number of ipv6 ping/pong responses. This can prevent the enr-auto-update from finding and updating a node's ENR to its external socket.

For security reasons, we can't just accept PONG responses from any node on the network. For this reason, we only ping peers that make it into our routing table as a number of security measures must be passed for a node to enter the table. However if the table is full, we reject peers from entering and therefore do not attempt to PING them.

This PR suggests the following mechanism:
If a peer fails to make it into the routing table, and we are lacking votes on either IPv4 or IPv6 and this peer can add a vote AND they are an outgoing peer (i.e one that we have chosen to connect to, for security reasons) then we ping them to get an extra vote for our external address.

[AgeManning]

cc @pawanjay176

@ackintosh - What do you think of this logic? Is there an easy way to test this with the current infra?

[ackintosh]

Currently, we accept a PONG response as a vote only if the node exists our routing table. So the PONG response is ignored even if we PING a node that failed to make it into our routing table. We should also change this condition?

discv5/src/service.rs

Lines 816 to 818 in 765abac

	self.kbuckets.write().entry(&key),
	kbucket::Entry::Present(_, status)
	if status.is_connected() && !status.is_incoming());

[ackintosh]

I think Testground doesn’t support IPv6, so we can build a test environment based on Docker Compose. It might require a little work, but I’ll give it a try.

[AgeManning]

ah nice! Thanks for the catch!

I've modified the logic a bit to also just do this if we are in DualStack mode.

[jxs]

LGTM age, left some suggestions