CREST-10655: add tyree to docker-compose.yml

This resolves the issue reported in CREST-10655, that summit-tyree is being started by SIAB even when not selected.

The problem was due to the fact that the tyree app was not configured in docker-compose.yml, but the generated docker-compose-override.yml includes overrides for the tyree-app service because (because tyree is configured in the summit-env manifest). Apparently Docker Compose doesn’t care that the override mentions a service that doesn’t even exist, so it runs the image. However, because there’s no base config for it, even though the app is running, you can’t access it with a browser -- the proxy has no knowledge of the tyree container.