Feature/env var based config

[ChrisWeissmann]

Making the variables that are used to connect to the database, cached etc configurable via environment variables. Needed to do some extra work to make sure they aren't case sensitive, since there is direct mapping to the field names in the javascript object. Environment variables should be prefixed with CITRINEOS_ Configuring the message broker would look like: CITRINEOS_UTIL_MESSAGEBROKER_AMQP:...
Dots in the object are _ in the environment variables.

`

[thanaParis]

The process appears to be, look at the environment for variables and then use those preferentially over the values in the system config from the code, correct?
I did previously dabble in something similar to this here.
It checks for an environment variable if there is a value missing in the system config, specifically for the db user/pass.

I think we should remove my take above, it doesn't make sense to check for environment variables twice. However, I think the new solution should go in its own file in the same folder as the above in Base. I think it should to apply to all configs, not just the new one you made. We should add a javadoc to the defineConfig method that explains this behavior.

We should apply this new function inside defineConfig where the old logic I wrote is. This way, environment variables can apply before the config is validated, permitting required sensitive info like user/pass to be set in environment variables rather than code.

[ChrisWeissmann]

Yea, I like that approach, basically putting it a bit more upstream and deeper into where the config is being defined. I will give it a try.

[thanaParis]

Approved!