Enable ingestion via CDP in horizon verify-range docker image

[tamirms]

There is a verify-range docker image which is used to detect ingestion regressions in horizon release candidates. It works by ingesting a range of ledgers and then dumping the contents of the horizon history tables to disk. Then it repeats the same workflow but this time using the horizon release candidate. Finally, the output from both runs are compared. The job succeeds if the output from both runs are identical.

The verify-range job is effective in detecting regressions but it takes very long to run on full history. Also, the verify-range job often fails on tasks because it consumes too much memory. Both of these issues can be solved if we update the verify-range docker image to ingest from a GCS datastore of ledgers instead of using captive core.

[mollykarcher]

Alternative that was discussed at team meeting on 3/19 was to retire verify-range in it's current form (ex. running in separate AWS account via AWS batch), but to instead recreate the same verification behavior using Stellar ETL, as is being done to verify TTP.