prefix docker containers names

### User Story

I cookiecut two instances and I want to run them both depending on which project I am working on.

### Current result

The second ``docker-compose up`` will fail (containers already exist). This containers will need to be removed and recreated for the second project, because the ``./scripts/setup`` will get denied in the DB (wrong credentials).

### Expected result

I understand the services should be independent, but I don't want to have to change defaults of rabbit/redis/db/es for each instance. However, if the containers names(?) are prefixed with e.g. instance name this would not happen. The second ``docker-compose up`` would not fail and both could co-exist.

### Possible drawback

End up with 20k services running, but is up to each one of us to control that I guess.

Start by inspecting the generated docker-compose configuration and how service container names are defined for a cookiecutter instance. Verify the behavior with two generated instances, and consider the work complete when both can run concurrently without container-name collisions or manual changes to the default service names.

Written by the indexing model from the issue text.