[DEVOPS-301] Make testing services optional.

[barbun]

Issue

The scaffold ships with two container definitions that increase the start time of the docker compose stack. These are used only by a handful of customers. To reduce the pipeline consumption usage by projects, we should make these opt-in only.

Proposed solution

Comment out the services and adjust the build commands.

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (3)

docker-compose.yml:138

• The instructions in the commented out block imply that both test and chrome services should be enabled together. Please add guidance or a note indicating that uncommenting only one of these may lead to dependency issues since the chrome service depends on the test service.

# Uncomment to enable testing.

.ahoy.yml:9

• Switching the wait command from the 'test' container to the 'cli' container is a critical change. Please verify that the cli container is properly configured and ready to handle this waiting logic, ensuring it truly replaces the original behavior.

docker compose exec -T cli dockerize -wait tcp://mariadb:3306 -timeout 2m &&

.ahoy.yml:29

• Ensure that using the 'cli' container in place of the removed 'test' service does not negatively affect the expected timing or initialization dependencies in your pipeline.

docker compose exec -T cli dockerize -wait tcp://mariadb:3306 -timeout 2m &&

[jackwrfuller]

Just noting here that this relies on adding dockerize to the upstream govcms image ("cli"), which is done here: https://github.com/govCMS/lagoon/pull/488/files