WIP: replace scheduler log sidecars for progrium/logspout

The reason why this shift is necessary is because some schedulers don't give the user direct `docker` CLI access. Attaching to the socket and retrieving logs is the recommended way of doing this, and conveniently enough, progrium/logspout does exactly that. Swapping out the log sidecars for logspout will help us move in the direction for better compatibility with other schedulers.

Still to do:

- [ ] provision progrium/logspout on every host
- [ ] massage incoming messages for application names (instead of `humble-fireball_v2.web.1`)
- [ ] investigate proper message format coming into deis/logger (looks like `2014-07-31 19:03:03  2014-07-31T19:03:03Z aa2e7309f8e4 humble-fireball_v2.web.1[1]:` which has some redundant data, unknown information, etc.)
- [ ] fork progrium/logspout (not necessary, but up for discussion so we can maintain our own fork and contribute upstream like we do with slugbuilder/slugrunner)