Turn Utility Scrape into one Monthly CRON Job

[FraserTooth]

Right now, each utility scraper needs to be run individually. This should be handled by a single monthly CRON job
Requirements:

• One single, well-named endpoint.
• Stick to serverless for the schedule definition
• If an Error Occurs on a given scrape we should move to the next utility but log the error
• It should be clear which utility was in error
• We should log whether new data was available for the utility.

Notes:

• We cannot guarantee that the utility files are available at midnight on the first of the month (or first of every 3 months, as some are), as the process does not appear to be automated, so make it update on the 2nd.