feat: migration use of docker compose and env by file

[rv2931]

The goal of this PR is :

• redesign docker environment set up for dev and test at least, production basics eventually
• create/modify docker compose file(s)
• Update Makefile and proposing homogeneous and simple targets

For docker compose:

• manage build
• describe directly the environment un docker-compose file
• manage dev/test environment at least
• manage secrets
• design an init job (Check DB availability before starting app, Check/Update DB structure ?...)
• Design maintenance job (load data if mounted, some clean if needed, ...)

Don't hesitate to add/correct things

[rv2931]

abandonned as Proposed environment management is not really compliant with the actual wanted functionnality of docker compose that load automatically .env file
For information, this .env can be changed by changing COMPOSE_ENV_FILES env vars (Ex: COMPOSE_ENV_FILES=.env.test)

Another way to switch of environment file is to explicitly give env filename to use with --env-file option
docker compose --env-file .env.test

A smart way to se this to use BLOOM_CONFIG env car that is managed by bloom.config for native deployment (Ex export BLOOM_CONFIG=/project/.env.local.deploy && /venv/bin/python app.py) and to declare a local use alias to replace "compose" commande by "compose --env-file=$APP_CONFIG"
With this third configuration you can switch easely from nativ deployement to docker deployement with 2 dedicates files but easely switch by changing APP_CONFIG value

Launching test instanse with Docker and using compose alias

- alias compose="compose --env-file \$APP_CONFIG"
- export APP_CONFIG=.env.docker.test
- docker compose up
- export APP_CONFIG=.env.local.prod
- /venv/bin/python app.py