Feature/vote 2874 downsync workflow improvements

[tt-gsa]

Jira ticket

VOTE-2874

Description

Implement improvements to downsync workflow.

Deployment and testing

QA/Testing instructions

1. Allow the scheduled backup to run in the production environment.
2. Confirm a latest.sql.gz is created in the top level of the prod directory in the backup S3 bucket.
3. Run the downsync-backup workflow to create a manual backup of the prod database by manually triggering a pipeline with key/value: backup/prod as the pipeline parameters. This will need to be ran when the upkeep workflow is not running as either a pipeline or cloud.gov task.
4. Confirm a latest.sql.gz has been created in the top level of the prod directory in the backup S3 bucket with an updated timestamp from the previous one.
5. Run the manually triggered downsync-restore workflow in a branch specifying key/value: restore/<env name> as the pipeline parameters. For example, restore/stage for restoring the latest prod db backup into the stage env.
6. Confirm workflow completes successfully and the stage env is backed up (for this example).

Checklist for the Developer

• A link to the JIRA ticket has been included above.
• No merge conflicts exist with the target branch.
• Automated tests have passed on this PR.
• A reviewer has been designated.
• Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

• The file changes are relevant to the task objective.
• Code is readable and includes appropriate commenting.
• Code standards and best practices are followed.
• QA/Test steps were successfully completed, if applicable.
• Applicable logs are free of errors.