[WIP] Spike out how the chat deploy interface might work

:construction: Work In Progress :construction:

![10](https://cloud.githubusercontent.com/assets/550256/4188376/04b8ab08-3772-11e4-94a4-4ae12d16f24a.gif)

Example: `botzo ship heroes 1.0.0 production`

Assumptions: 

- [x] repo exists at `articulate/heroes`
- [x] tag/release `1.0.0` exists (ref can be a tag/branch/sha but tags are preferable) 
- [x] production environment exists
- [ ] ship api is awaiting commands at `HUBOT_SHIP_URL`
- [ ] ship api accepts `/deploy/:app/:env/:ref`
- [ ] ship api runs:

`cd /path/to/$APP && git pull && git checkout $REF && bundle exec cap deploy $ENV`

Future maybes:

* chef runs would be kickable from here `botzo ship chef-heroes 1.0.0 production`
* merge PRs, tag/release process from `botzo ship merge heroes 23` `botzo ship tag heroes 1.0.1`
  * related is ability to auto-spin up CI/QA envs when a new PR is opened, use github deployments api to push status back to PR with URL to a freshly Cheffed env with PR's branch deployed, when PR is merged/closed, temp server is shut down