Improve documentation on JOC Cockpit logging capabilities

Current Situation

• The JOC Cockpit - Logging article explains use of log files by JOC Cockpit.
• The article does not explain use of log levels and logging capabilities for specific scenarios, e.g. authentication, certificate handling etc.
• The information how to apply log levels for individual scenarios is scattered across a number of articles, e.g. Authentication and Authorization - Configuration

Desired Behavior

• The JOC Cockpit - Logging article should be improved to
  • reflect logging scenarios for
    • authentication including LDAP that is activated by log settings such as

      log4j.logger.com.sos.auth=debug, shiro
      log4j.additivity.com.sos.auth= false
      

    • certificate handling including handshake information. Such log information is currently available with the -Djavax.net.debug=ssl setting that has to be added to /etc/default/joc.
    • cluster fail-over including detailed information of session hand-over between JOC Cockpit instances
    • database processing
    • enable request log
    • optionally other scenarios for detailed logging
  • clearly explain the steps to apply changes to log settings, e.g.
    • when a restart (or stop/start) of a JOC Cockpit instance is required
    • when a restart of all JOC Cockpit instances in a cluster is required
• The log4j.properties file that ships with JOC Cockpit should included a number of sections (in comments) that can be activated for the respective logging scenarios.