fix(builder): exec the runner
fix(builder): Non-root slugrunner and slugbuilder

This improves the compatibility to heroku and stops running apps as root
fix(builder): Reverted to default php buildpack

The pervious compatibility fixes made the heroku php build pack work
out-of-the-box again
feat(router): image without development libraries to reduce the size.
fix(router): build cleanup.
fix(router): ubuntu-debotstrap doesn't have netstat and confd errors are redirected to /dev/null.
fix(router): use ubuntu:14.04.
fix(logger): don't print a message on every incoming message

For example, if we receive a message from deis-logger itself, it
will print it, which will then log it, then print, then log... You
get the idea.
fix(logger): add more verbose message
fix(logger): log the error, but don't panic

We should not panic if we cannot find the app name in the message.
ref(tests): update details in CI node setup script
fix(scheduler): allow proctypes with dashes and underscores
Merge pull request #1983 from mboersma/test-setup-tweaks

ref(tests): update details in CI node setup script
fix(controller): Use correct entrypoint for run

Running commands in an image build using git push requires to use
‘/runner/init’ as entrypoint, otherwise environment variables inject by
buildpacks are missing.

Fixes #1801, fixes #1568
style(logger): go vet
Merge pull request #1972 from johanneswuerbach/buildpack-env

fix(builder): Non-root slugrunner and slugbuilder
docs(installing_deis): remove xip.io instructions for ELB

xip.io simply doesn't work for ELBs - it returns an IP of
54.64.0.0 which obviously isn't a valid IP.

I suspect it works for CNAMEs in general, but not for CNAMEs
which resolve to multiple IPs, as ELBs do.
Merge pull request #1985 from johanneswuerbach/run-env

fix(controller): Use correct entrypoint for run
Merge pull request #2003 from carmstrong/remove_xip_io

docs(installing_deis): remove xip.io instructions for ELB
chore(builder): migrate to cedar-14 stack

With quantal coming out-of-support, heroku implemented the cedar-14
stack. This stack is what's used on heroku in production today AFAIK.
Migrating over to this stack makes us more compatible with Heroku.