Avoid leaking unhandled rejections

[shicks]

Fixes #393.

Previously the callback-based API leaked unhandled rejections in two places:

1. After calling the callback, it rejected the unreturned promise, which is never handled. This is fixed by returning between the callback and the reject.
2. While watching, the first build unexpectedly returns a promise reflecting the initial result. If it's failed, it's likely to go unhandled, but also doesn't ever call the callback anyway. This is fixed by passing the callback for failures, such that the returned promise is the (probably-successful) result of the callback, rather than the error itself.

[webketje]

I've reviewed these changes locally. I haven't added unit tests yet, but I feel this is already sufficiently valuable to include in a patch release, thank you!