Oops, another data file git shouldn't care about.

Honestly I don't recall why we added retries here...

  https://gitweb.torproject.org/doctor.git/commit/?id=5e200e9

Seems this mostly just masked when an authority was unavailable.

During our recent dev meeting David Goulet asked me for a DocTor check for
relays rapidly changing their fingerprint. Doing so likely means they're trying
to get into a privilaged position to snoop on hidden services.

Plan is to keep an eye on this script for a bit (just whipped it up, no doubt
it has issues), then send the results to David when we have some confidence in
it. Later the results will be sent to bad-relays@.

Notifying authority operators in addition to tor-consensus-health@. Folks with
public contact information are notified via cc, while and others via bcc.
Contact information is specified in 'data/contact_information.cfg', which we're
keeping out of git to hide private addresses.

This necessitated reverting a change I made to sidestep OOM issues. If that
starts biting us again I'll need to figure out another method for addressing
it...

Same check as DocTor except that we also check for extra authorities reporting
measured bandwidths (good thing to do since we need to stay in sync when new
bandwidth scanners are spun up).

Having the known parameters in code has been bugging me, so moving it and the
messages to a configuration file.

Our consensusTracker.py was petty slick, but most of what it does is
unnecessary. The html formatted emails were pretty, and the stats were kinda
interesting. But the only true usefulness of the script was to notify us of
sybil attackers spamming us with relays. Replacing it with a far smaller,
simpler script that just does that.