Restore Docker Daemon logging levels by suppressing confidential user config.json information

Currently the Docker Daemon dumps the contents of a user's config.json file into the zCX joblog (SYSPRINT) if there is a syntax error in the Dockerfile (e.g. missing "\" continuation on RUN command or perhaps other situations). The user's config.json file may contain sensitive/confidential information, such as the http/s proxy string with a userid/password in the clear. When in SYSPRINT all authorized operators can see the proxy id/password.
This is in contrast to the unix permission settings that protect config.json from other users.

The only current option is to disable Docker Daemon logging for the entire instance, by setting the Docker Daemon Logging option to "fatal" (essentially almost no logging).

This effectively disables the other existing logging levels options of info, debug (default), warn and error.

The idea here is to re-enable docker logging options by filtering out confidential information with the standard "XXXXX" for fields such as password. Ideally there would be a new radio-button (yes/no) option to "suppress confidential config.json information" in the zCX instance configuration options. So people

Restoring the logging options has benefits. Running with "fatal" suppresses many useful messages for both developers and system admins, making the system more difficult to maintain stability/availability. If using "debug" option today, a security risk finding is needed. This idea would remove the risk finding, making security reviews easier.