Error Handling

[AavHRF]

Raised partially in #32 -- the error handling for the API calls is lackluster at best, and could probably stand to be upgraded. Same for the daily dump. Ideally we should use .raise_for_status() as @esfalsa indicated in #32, and it should be used on every API call in order to catch bad data before it corrupts the program run.

Other potential options include manually parsing out the HTTP status code with an if block, which would give us the advantage of being able to fine-tune responses for various codes. This is also the moment where I note that we don't bother to do anything if the API returns a 429. That should probably be changed.

This issue should not be closed out until the following items are resolved:

• Raise requests error on HTTP error code #32 is merged
• Error handling is added to the founderless and passwordless API calls
• The error handling terminates the run on a HTTP 429 code
• Error handling should be added to the daily dump download (flashbacks to v2.0.2, anybody?)
• Don't crash in CLI mode if the dump doesn't exist (Download dump in CLI mode if not found #36 fixes this)

[AavHRF]

Gah, I forget that automation closes this. Reopening.