Check that onion services have successfully posted descriptors before verifying
Before verifying, chutney checks that:
- each relay descriptor is cached at each node
- each relay is in a consensus, cached at each node
- each relay is in a microdesc consensus, cached at each node
- each bridge descriptor is cached at each bridge client
We have other tickets for checking:
- cached bridge descriptors at the bridge authority
- the bridge networkstatus That just leaves onion services.
Onion services are tricky, because they post to some HSDirs in the network, but not all. And those HSDirs don't cache the onion service descriptors in a file.
So here is one possible design for this feature:
- check each onion service log for a successful descriptor post to at least one HSDir
- check v2 and v3 onion services
- call it an extra 200% "bootstrap" stage (because it's a sender log check, not a receiver cached file check)
- require 200% bootstrap for onion services