/reviewed-on !175

  Apache MPM Watchdog promise was introduced to search apache on
  deadlock state after a graceful reload and kill them after 600s.

  This change prevents the apache lack of nodes after several processes
  get stalled on deadlock.

  This can be used to define minimal metrics to the frontend to
  prevent mpm nodes starvation after gracefull restarts

  Wait for 60 to reload apache configuration in order to accumulate
  several logrotate runs.

  If the amount of slaves are too high, the number of logs are high,
  so the entries on logrotate are also high. So it is enough to DDoS
  with a huge amount of 'kill -1', so delay is the only way to avoid
  to re-implement logrotate existing features.

  Only reload the apache configuration if the the apache configuration
  or the certificates contains a change, else don't reload it.

  Keep a command on bin folder to force reload of configuration in
  case it is required.

  Allow http2 protocol be enable or disable by default
  Allow set certain configurations for MPM to control the number of process and threads.

  Apache verbose way too much with LogLevel info

  When slow clients post a large request, 30 seconds is too short for the current
  production usage. Short timeouts are rare but it always happens on POST, which
  is annoying for the user.

  Move from 30s to 5min the timeout to allow the slow clients upload their data
  with time.

  Include report for apache status (see mod_status on apache documentation)
  Include report to traffic server to produce a summary on cache
  Update report for ats for run only once an hour

  It is protected with monitor password.

This reverts commit b4e440ed

  Upgrade officially all SR to latest zc.buildout version.

If not so, trafficserver configuration is removed and then replaced on
every slapos node instance call making traffic server unstable