Netty streams should reduce the capacity of pooled buffers passed to sendFrame

When a small write and flush is passed through the framer we hold the full 4k of the buffer until the write completes. By reducing the capacity of a pool direct buffer to the readably byte limit we immediately release the unwritten portion of the buffer back to the pool.

This may or may not have an impact on performance and utility should be evaluated by bencmarking. It may improve performance by making more bytes available to thread-local allocation. The most likely benchmarks to be impacted would be streaming ones that write and flush many messages in a tight loop as it would alleviate buffer-arena locks.

Start by locating the Netty framer path that handles a small write and flush, focusing on pooled direct buffers and the readable-byte limit. Benchmark streaming workloads that write and flush many messages in a tight loop, and consider the work done when the unwritten buffer portion is returned to the pool and performance impact is measured.

Written by the indexing model from the issue text.