Support environment variables in configuration import

When I start CloverDX server in Docker (but probably not only there), I have a option to directly import configuration so that the server is fully operational. Part of configuration can be users with password, but I do not want to have these passwords in version control system with configuration. I want passwords to be in some secret management tool. It is common practice to pass values of secrets as a environment variable.

Import of configuration should support placeholders for environment variables. These will be replaced by real value of environment variable during import.

is there a way how to prevent these values to be displayed in server UI?
how does it work with passwords? we do transfer just password hash with configuration, don't we?

Acceptance criteria

• Import of CloverDX server configuration is able to use values of environment variables
• Such env variable can be used to configure password for user