[FEAT-Infra]: Resolve Flyway Migration issues in AWS

Currently, migrations (via the flyway container) are part of the chart-api ECS task definition, so migrations are only run if we push sctapi to ECR - if migrations fail, changes to the chart-api service (like api endpoint updates) will not be deployed - we won't know that changes failed to be deployed via the github workflow, as that only pushes to ECR, and doesn't watch any other downstream issues.

Because only chart-api has a sidecar, pushing chart-feat-api to ECR doesn't trigger migrations in any case, which will (and has) caused drift between the api and RDS db. We need to i) add a flyway sidecar to the chart-feat-api service as well, and ii) update the api GitHub deployment workflow to push both api images in one workflow (this will be done in #723).

Create a Jira ticket that requests the following:

• Add a flyway sidecar to the chart-feat-api service
• While we're here, enable DeploymentCircuitBreaker on both api services to automatically rollback to the last known good version in the event of a failed migration