Add resources to migrate-db container

When using ArgoCD for deploying Flagsmith, it thinks the cluster is not synced with the chart because it finds a diff, as the migrate-db container doesn't include a `resources: {}`.

I understand for a migration job which is short lived adding resources may not be relevant enough, but this helps avoiding sync issues with GitOps tools, and may also avoid issues with clusters that require all workloads to have resources defined.

This affects t he `deployment-api.yaml` (specifically the `migrate-db` init container) and the `jobs-migrate-db.yaml`.


Open deployment-api.yaml and jobs-migrate-db.yaml, focusing on the migrate-db init container and migration job. Review how resources are represented in the surrounding chart templates, then confirm the completed change defines resources: {} for migrate-db in both files and removes the reported GitOps diff.

Written by the indexing model from the issue text.