Update ZeroMQ support to provide inproc handling. Currently ZeroMQ support is broken as I try and find a reasonable way to get the shutdown/destroy/close to work without hanging. That's a very temporary situation however. I'm just pushing this now so I can link to it when I ask the experts how to fix it. :)
Revert a previous change that returned a Boolean from the Promise returned when writing data to a channel. After some discussion, it became clear that this is a suboptimal interaction and that it would be better to either complete the Promise with null, which means success, or complete the Promise with an exception, which signals an error. This means in the ZeroMQ support an exception has to be created since it only returns true/false to indicate a success or failure on write.

Also reworked the ZeroMQ support to allow for proper shutdown of ZContext objects. Also had to introduce a delay in the tests for inproc connections since they seem to fail if a client is attempting to connect to a server too soon.
Tweaking ZeroMQ tests to work in different CI environments.
Turn off logback appender loadtests.
Using 127.0.0.1 instead of the string "localhost" since it apparently means different things on different CI servers.
Create a dummy method for the AsyncAppenderTests
Trying to track down a not-reproducible error.
Use explicit localhost IP rather than hostname
Troubleshooting a strange error that only happens on build servers
Troubleshooting random TCP errors that only seem to happen on build servers
Lazily init HashWheelTimer since early instantiation at Environment init time leads to problems in STS where the object is reflectively instantiated but never cleaned up.
Add a more meaningful toString impl.
Change the way mapMany handles flushing. Add a test to make sure that data from returned Promises can be captured.
Fix a failing test.
Fixes #225 Moves the flush call into the event loop by adding a special handler just for doing writes. Now we write a Tuple of the data and a boolean of whether to do autoflush or not. The NetChannel.flush() is not implemented by writing a Tuple of `null` and `true` to force a flush.
Increase timeout for CI servers
Simplifying TCP interaction tests
Added a test to ensure values that pass a Predicate in a Stream.filter expression are not passed to the else Composable.
Add timeouts to ZeroMQ TCP tests
Troubleshooting ZeroMQ Context termination, which randomly hangs on CI servers