ooni-probe's bridge_reachability tests should require bridge fingerprints for the inputs
Requiring the input to have bridge fingerprints would help to partially fix issues like https://github.com/TheTorProject/ooni-pipeline/issues/17, and it would help to solve the problem where people doing data visualisation on the bridge_reachability report data are forced to display data for a bridge based on its IP:port (because no fingerprint, and thus no hashed fingerprint, is available). For example, this is currently the case for some of the bridges on https://beta.chokepointproject.net/measurements/tor-bridge-reachability#Bridge_explorer.
In fact, perhaps the sanitised reports should only contain the hashed fingerprint, neither the fingerprints nor the addresses? (Following the principle of avoiding handing others a loaded gun with the safety off.) (Although perhaps this should be another ticket.)