patch out blather exceptions, next_tick for jabber logging to remove odd delays

This probably warrants some discussion. I have some work in [another branch](https://github.com/ali-graham/flapjack/tree/threading_restructure) where the jabber gateway doesn't use em-synchrony, and it does become simpler.

After extensive review of the eventmachine docs and the blather source, the only way to handle things in the current codebase is to patch out the exceptions in the blather internals. If each blather client has its own EM run loop, as in the above-linked branch, we could just catch the exception outside the loop and restart the client without having to deal with the rest of the pikelets, but that's not possible as is.

Fixes #115 in somewhat hacky fashion.