Resolve "Streamline logging configuration by removing initContainer in favor COM_FORTIFY_SSC_LOG4j2_OVERRIDE"

General MR

Summary

Streamlines our log configuration story by:

• Removing a complex initContainer setup for overriding Fortify's log4j configuration
• Replacing it with use of the vendor-provided COM_FORTIFY_SSC_LOG4J2_OVERRIDE variable
• Reworks the .Values.ssc.config.log4j section to have two straightforward options:
  • .enableDebugConfig to install a lightly-tweaked log4j config that will 🅰 set the log level to debug and 🅱 print all logs to STDOUT.
  • .customXMLConfigString to allow for open-ended customization of the log4j configuration as needed.

Relevant logs/screenshots

ssc.config.log4j.enableDebugConfig=true

ssc.config.log4j.enableDebugConfig=false

ssc.config.log4j.customXMLConfigString

[CUSTOM LOGS HERE]!

Upgrade Notices

The .Values.ssc.config.log4j section has been streamlined — previous values will not work. See CHANGELOG or values.yaml for more on the current log customization options.

Closes #116 (closed)