Related to #450

NOTE This is a very simple change, but it has consequences that docker-compose will now name containers with 'gargantext' as prefix. I.e instead of docker_postgres_1 you will have gargantext_postgres_1. While container name change is not an issue, there is an issue however in also changing volume names: docker_garg-pgdata14 changes to gargantext_garg-pgdata14 which basically means you will get a fresh database.

I guess you could stop the docker container, rename volume (e.g. https://www.commands.dev/workflows/rename_docker_volume but I didn't test this) and run docker-compose with the new project name.