feat: bootnodes healthcheck CI (& generator/aggregator?)

[meowsbits]

Bootnodes are nodes that "cold" clients (protocol providers) use to establish a connection with the peer-to-peer network. Inadequate bootnodes for a network can cause either slow or impossible network connections.

Bootnode lists are currently hardcoded for each supported network. But liveness (useability) checks are never systematically undertaken, which can cause p2p issues if the lists get invalidated. The current system for bootnode addition is essentially that a node or nodes are proposed, a developer reviews the proposed enodes by pinging them manually (over an arbitrary and variable time course), and then approves the addition. Same, but backwards, for removal.

This feature prop wants to establish a system for

• [ ] bootnode list health checks to be undertaken systematically via a CI environment, where given parameters, inadequate bootnode lists can be flagged for review, purging of dead nodes, and addition of new ones
• [ ] ideally, an environment which could not only provide a health check, but also provide information that could be used in the generation of healthy lists

This would remove tedious developer burden, reduce connection failures, and, in essence, move toward systematizing variables for a critical first process for all devp2p networks.

[soc1c]

what about bootnodes that are temporarily offline?

[meowsbits]

Bootnodes should not normally be temporarily offline ("You had 1 job..." :joy_cat:) . And if and when they are, it should be for short enough periods that the chances of coincidence with reachability tests should be very small (assuming we don't want tests that intentionally run for v long times).