Bugfix to !135 — more resilient location for custom log4j2.xml config file

General MR

Summary

!135 (merged) seems to be failing in some situations due to a race condition. This MR rethinks the previous approach to installing custom log4j XML configs; rather than using an initContainer to layer in the desired ConfigMap at boot time we are instead mounting our custom ConfigMap over the file source that Tomcat/Fortify copy in as the default config on each boot.

Adds a CI test to confirm that the expected log4j config is in force in the container — see tests/wait.sh.

Relevant logs/screenshots

Config-pinning init container's log output

Debug logs in force in the webapp container

local run of ./tests/wait.sh wait_project against my test cluster

Linked Issue

fortify#52

Upgrade Notices

N/A