Replace AppendableByteArrayInputStream in DirectDruidClient

* Replace with SequenceInputStream fueled by an enumeration of ChannelBufferInputStream which directly wrap the response context ChannelBuffer
* Added zero-length byte array when DirectDruidClient is done. This prevents an odd race condition on `done`.

(old pull request didn't like the force)
I'm worried that having an arbitrary timeout will cause issues with long-running queries that stream results back. Why do we need a timeout at all?