compose: Unset container_name for all services

[phoevos]

Remove hardcoded container names from all services in the docker-compose files to allow multiple instances of the same service to run in parallel without conflicts. This is important to allow both scaling individual services as well as running multiple instances of the CMS stack locally for testing purposes.

Set the top-level project name in the docker-compose files so that it can be used as the default prefix for container names. Use cms for all stacks apart from the load tests (i.e. cms-load) and the dev deployment (i.e. dev-cms). The project name can be overridden on deployment through the -p command line flag or by setting the COMPOSE_PROJECT_NAME environment variable.

Note: Information that was previously only conveyed through the container names (e.g. model names for mlflow-models) was moved to a dedicated label. Apart from that, the MLFLOW_BACKEND_STORE_URI environment variable that is used to configure the garbage collection cronjob in the MLflow server was edited to use the mlflow-db service name instead of the container name (matching what we were already doing in the MLflow server startup script)

[baixiac]

LGTM. Can this also ensure container names follow the old cms prefixing style rather than use the project folder name?

[phoevos]

@baixiac I've set cms as the top-level project name in the compose files to be used as the default prefix, but this is probably something that should be specified on deployment with the project name flag or environment variable to differentiate between environments.