Rework how we setup logging for Crowbar [2/2]

There are two main changes:

  - instead of putting stdout/stderr in production.log, we put them in
    production.stdout and production.stderr.

  - we really use production.log to log things, instead of using syslog
    which loses the formatting and spams /var/log/messages.

The rationale for using syslog was "distributed setups", but since we
put the logs of chef-client runs in /opt/dell/crowbar_framework anyway,
I don't think this rationale stands.

Crowbar-Pull-ID: b381b3bca3dd6482b6c462570095828859ba5a08

Crowbar-Release: pebbles