Allow web-hooks to be configured to fire on test or deploy

Fixes #5

I figured out why my web-hook wasn't firing after deploy. The worker was only listening for `job.status.tested`. So I added a listener for `job.status.deployed`. Instead of reusing `test_exitcode` I add a new property to to the payload `deploy_exitcode`. I also changed the output to say which webhook listener is being fired. 

I tested this on my fully updated strider. However I had to remove strider-sauce to work around #4
It is there to register the deploy listeners after the tests pass. If you register the deploy listener when the test listeners are registered and tests fail you will orphan the listener and it will fire two web-hooks on the next deploy. I guess I could check the payload to see if tests failed to remove the listeners but this seemed cleaner.

I'll see if I can think of a way to refactor.