Supervisord

Run bamboo and haproxy separately in supervisord in docker container.
failure of bamboo won't have affect on haproxy instance and bamboo can meanwhile safely restart.
There might be a typo? is it suppose to be `CONFIG_PATH-:config/production.example.json`
` -config=${CONFIG_PATH-config/production.example.json}`

Since bamboo is now managed by supervisor, it might be good to expose supervisord log to stderr/stdout. This helps to trace those callback or configuration issues:

- add `loglevel=debug` under `[supervisord]`
- add `redirect_stderr=true` under `[program:bamboo]`

full example: https://gist.github.com/activars/0de50c1cf61c77ca4375