Fix unhandled promise rejections when a trigger errors

[abrenneke]

When a trigger, such as the callback to controller.hears(...) errors (the async callback rejects), this promise is not handled correctly, and results in an unhandled promise rejection.

This is because the run function for ware does not support promises (the middleware themselves do, but not the callback).

I don't really agree with the decision to use a non-promise-supporting library like ware in this very promise-based framework, but we can at least promisify those calls.

This ends up simplifying a lot of the code that uses the middleware, as Promise constructors no longer need to be used.

With this fix, the promises bubble up all the way to the handleTurn function, and can be handled at the web layer.

Maybe a controller.on('error', () => {}) event would make sense as well. Or an error middleware?

[ghost]

All CLA requirements met.

[abrenneke]

Now that I think about this a bit more, it seems based on the behavior of ware that middleware can't abort the request by not calling next(). It will continue the request regardless, not sure if that's intended behavior. They can throw an error, I suppose.

[alex-ubitec]

I've encountered similar problems as well.

[alex-ubitec]

That PR doesn't fix the problem.

Please take a look at the promises that this PR tries to change, because they are simply written incorrectly. The suggestion to use promisify is just to prevent those errors from propping up again, but you could just wrap the code inside the new Promise calls with a try-catch as well.