Rewrite Streaming HR client operations

Streaming operations today require exclusive control over a netty channel for the entire send or receive operation. This is wasteful of resources and prevents us from using a single channel for something like ISPN-14868.

Also another thing is streaming operations set a timeout, but it is immediately ignored as we immediately complete the operation. But the operation is still registered with the HeaderDecoder. This means that it can timeout, but even if it does it will do nothing as it is ignored as the stage is already completed.

Also errors with the channel are not reported until the user calls the close method on the returned Input/OutputStream. We should be able to propagate this sooner.