Create ingestion functionality for a scope config #8
Description
Expanding penums ingestion to accept a "scope config"-esque file would improve automation required for targeted launch and allow for potential integration into other tooling.
Possible parameters/types of configs:
- Top-level domains
- ASN (in conjunction with TLD or by itself)
- H1/BG scopes
- Service specific, e.g., web servers
Config will most likely take the form of a JSON.
Rate limiting and timeouts pose an issue to scalability; code should be refactored to improve scalability before this (or else this would work, but take forever / produce poor results). See #9