Spike: Consider automated re-deployments to test/prod

[exalate-issue-sync]

I got this idea from:

In addition to deployments after code change, we generally need to (automatically) re-deploy daily to ensure the running containers haven’t been tampered with (an ATO compliance requirement). See CircleCI’s [

“schedule” docs

](https://circleci.com/docs/2.0/configuration-reference/#schedule) for details.

• Circle cost, research usage?
• What cadence API/App/Proxy etc? M-F? Weekly?
• Keeps builds fresh

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1883