Streamline logging configuration by removing initContainer in favor COM_FORTIFY_SSC_LOG4j2_OVERRIDE

Background

Follow-on work after successful completion of #52 (closed).

While we now have the ability to enable debug logging to STDOUT in Fortify the way it was implemented required a lot of indirection. Now that we've learned of the COM_FORTIFY_SSC_LOG4j2_OVERRIDE environment variable we should be able to use that instead of our current initContainer approach.

Recommended tasks

• remove the log4j-config-pinner initContainer
• add a new stringy helm value to allow for passing in a multiline string as the intended contents of a custom log4j2.xml config file
• if the helm value is not empty, mount the contents in as a file somewhere on the container's disk and set COM_FORTIFY_SSC_LOG4j2_OVERRIDE to point to that file
• Once this is worked out, review tests/wait.sh to see if it should be removed altogether or simply rewritten