Understand best way to pass DB environmental parameters to containers in workflow

[GernotMaier]

The current somewhat cumbersome way is:

• set DB environment variables similar to simtools by source set_DB_environ.sh
• run cwltool with cwltool ... --preserve-environment DB_API_PORT --preserve-environment DB_SERVER --preserve-environment DB_API_USER --preserve-environment DB_API_PW --preserve-environment DB_API_AUTHENTICATION_DATABASE ...

This is not ideal and an easier way should be found.

cwtools prints a warning, which we probably can ignore:

WARNING You have specified '--preserve-environment={DB_API_PORT, DB_SERVER, DB_API_USER, DB_API_PW, DB_API_AUTHENTICATION_DATABASE}' while running a container which will override variables set in the container. This may break the container, be non-portable, and/or affect reproducibility.