Use real services for integration test

At the moment, we don't run _real_ services in integration tests. Instead, we launch services in Go tests. This is not ideal since it doesn't provide test coverage on the real container images we release.

Per https://github.com/abcxyz/jvs/pull/157, we had a bug in the dockerfile that caused bad container images. The integration test didn't catch that and we only realized the issue when we were trying to deploy the images.

Look at the existing integration tests that launch services in Go tests. Understand the project's Dockerfile and container images. The goal is to modify the test setup to use real container images instead of in-process services. Check for any existing CI/CD configuration and how tests are currently run. 'Done' means integration tests pass using the actual released container images.

Escrita pelo modelo de indexação a partir do texto da issue.