TorCtl.ConsensusTracker should track NS events too
We need to have two modes for TorCtl.ConsensusTracker, one mode that just tracks the actual consensus router set, and another mode that tracks the set of routers the Tor client actually believes are running. There may also be a bug in the Tor client that causes it not to generate NEWDESC events for routers it thinks are not Running..
TorBEL and the scanners need to use this first mode, but the script for 1919 needs to use the second mode.