fix(deploy): deploy test ECS by uploading images over SSH

[c1trua]

Background

The previous test ECS deployment flow relied on pushing images to Docker Hub and pulling them from the server. That was unreliable in the current test environment and also made deployment results hard to verify.

Changes

• switch the test deployment workflow from Docker Hub push/pull to build on the GitHub runner, upload images to ECS, and load them locally
• upload docker-compose.yml, deploy.env, config.yaml, and image archives to /opt/cixing over SSH
• pin dependency images used by the deployment workflow and compose file
• add stricter API verification after deployment:
  • ensure the API container is created
  • ensure the container is running and healthy
  • verify /healthz inside the API container
  • recheck API stability after a short warmup period
• improve workflow logs so deployment progress and final API status are visible
• fix the migration step so it does not consume the remaining SSH heredoc input
• clean stale compose state before deployment and remove uploaded image archives after a successful deployment

Impact

• test ECS deployment no longer depends on Docker Hub access from the ECS server
• deployment success now reflects actual API startup and health more accurately
• no application business logic changes

Verification

• docker compose --env-file <temp-env> -f deploy/compose/docker-compose.prod.yml config
• make -f Makefile/makefile lint
• make -f Makefile/makefile test
• manual deploy-test workflow run succeeded
• workflow logs confirmed:
  • migrations completed
  • API container started
  • API container reached running and healthy
  • /healthz returned 200
• browser access to http://<test-server>:8080/healthz succeeded