Release http(content)/http2(frame) bytebuf to prevent memory leak

[lcybo]

As the last handler that accessed the http data(bytebuf), Jersey handler has the responsibility to release them.
That require support for releaseOnClose in ByteBufInputStream since 4.1.7.Final.
Drop by to construct http2 pipeline via builder style.(detail)
Bump the version of netty to 4.1.30.Final.

[jansupol]

Filed CQ for Netty 4.1.31

[jansupol]

There is no valid ECA on file for [email protected]. Can you please sign the ECA?

[010gvr]

@lcybo @jansupol Not sure if this PR is still actively being monitored. But adding ChannelHandlerContext to a data processing class (NettyInputStream) feels a bit out of scope. Also, further load testing of current implementation revealed even more problems with JerseyChunkedInput and built in buffers leading to timeout and other related overheads. I've addressed several of these in #4312 which may be a permanent fix to all of netty/jersey issues that has been tested at a large-scale production use.