Ingest metadata useful for data visualisations and explorer

[hellais]

There is some data that is not generated by OONI, but is quite useful to have inside of the database (and synched in some way) to support some data visualisations as well as explorer.

I think ooni-pipeline is possibly the correct component that should be responsible for ingesting this data, but maybe @darkk has a different opinion on this.

The sort of data I am talking about is:

• [x] Citizenlab test lists - all the URLs, the category codes with description - update frequency: days
• [ ] ASN data - ASN, network name, other support data from peeringdb - update frequency: weeks
• [ ] Country data - iso alpha_2, alpha_3, country name, UN region name, CIA factbook data (or other similar source), wikipedia link - update frequency: months

Maybe also:

• [ ] Extra details for sites (see: https://github.com/TheTorProject/ooni-explorer/issues/56) - update frequency: days
• [ ] Shapefiles for countries (useful for doing privacy preserving location lookup) - update frequency: months

[bassosimone]

@hellais In principle I think all of this makes sense to have into the database. I was wondering whether you plan on keeping just the latest version of "resources" or to also keep some history. For example, later on in time it might be useful to have ASN data. Is historical ASN data already available through peering DB or not? My argument is that this may be useful later on to study existing data.