protocol 23: regression testing, run verify-range from genesis using datastore not captive core

[sreuland]

What problem does your feature solve?

run verify-range image for last horizon-v22.0.3 release and protocol-23 branch for full history

What would you like to see?

• merge services/horizon/docker: cdp enabled verify range image #5736 first to get the updated verify-range image into master
• merge master back to protocol-23 branch, so that verify-range command has datastore option
• run the verify range jenkins job from genesis with BASE_BRANCH=horizon-v22.0.3 and BRANCH=protocol-23.
  • specify the latest batch job definition for second half jobs which has the gcs datastore config.
  • the job defintion uses latest stellar/horizon-verify-range image pushed after services/horizon/docker: cdp enabled verify range image #5736 merged to master.
  • horizon-v22.0.3 tag should work when used as BASE branch on the new verify-range image which includes datastore config environment variables since the BASE branch will use db reingest which horizon-v22.0.3 will already have support for sourcing the datastore config params from env variables in place.

What alternatives are there?

[sreuland]

This is in review now:

• merged cdp verify-range to master
• ported master to protocol-23

And have kicked off a full genesis verify-range jenkins job/143 which uses a job def config'd to use cdp.

first and second half jobs related to the jenkins job have been started in cloud batch, and will need to be monitored to see how they turnout.

[sreuland]

kicked off newer verify-range jenkins job/144, had to update first and second half job/queue definitions in the batch setup.

[sreuland]

closing, completed aws job reconfig and re-run with datastore.