Spike on updating AWS IP ranges

[mrotondo]

Couple problems with the approach I've taken so far:

1. AFAICT classes have not been been loaded when the application.rb initializer runs, so using a Service class to package up the initial IP range loading doesn't work. Not sure of a great resolution for this yet, other than possibly requiring the class explicitly in application.rb.
2. Running Rails.application.configure in a DelayedJob seems to configure the job's (or maybe the job runner's?) application context, rather than the web server's (I'm about 85% sure this is what's happening). Thus, it isn't able to directly modify the web server's trusted_proxies configuration. The resolution for this is to call the service from a webhook action so that it runs in the web server's application context.

[github-actions]

Heroku app: https://gyr-review-app-5503-0040b9749b9f.herokuapp.com/
View logs: heroku logs --app gyr-review-app-5503 (optionally add --tail)