[#942] Add an option to disable decoding of chunked transfer encoding in HttpObjectDecoder
Add RxtxChannelConfig and tighten up visibility. Also support method chaining
[#962] Read data as soon as it is present in OIO and not wait till it match Buffer.writableBytes()

- Also add a new abstract class called StreamOioByteChannel which can be used by OIO channel implementation which are Stream based as a starting point.
[#963] Fix invalid free-up of messages if they are only passed-throught in HttpContentEncoder and HttpContentDecoder
[#965] Allow to adjust the SO_TIMEOUT on the fly
Rname StreamOioByteChannel to OioByteStreamChannel
[#957] Netty/Transport/RXTX: Add an optional wait time after opening the serial port but before configuration to allow the serial microcontroller to reset itself after opening.
transport-udt tests should run only when provider class can be loaded and initialized
[#964] ByteBuf.readLine() must return null when no more data is available in ByteBuf
*ChannelBuffer* -> *ByteBuf* and ChannelBuffersTest -> UnpooledTest
Bootstrap thread safety

Changed options and attrs from LinkedHashMap to ConcurrentHashMap to
avoid a possible ConcurrentModificationException if a thread was
adding/removing options/attrs while another was calling Bootstrap.init()
or Bootstrap.duplicate()
[#972] Correctly mark the ChannelPipeline once a ChannelHandler was removed and because of this a buffer was freed
Revert "[#972] Correctly mark the ChannelPipeline once a ChannelHandler was removed and because of this a buffer was freed"

This reverts commit 4ac3bace0f0578f8b84b3d3a2334d36448447f37.
[#976] Fix exception which will be raised by ChannelInboundHandler.discardInboundReadBytes() and ChannelOutboundHandler.discardOutboundReadBytes() if the handler remove it self from the pipeline
[#977] Stop processing messages/bytes in a loop when the handler was removed from the ChannelPipeline
[#973] Use static IdleStateEvents to reduce GC pressure
Disable test as this let fail the build 80% times on osx and slow linux servers. Need to investigate
[#986] DefaultChannelHandlerContext.fireUserEventTriggered(...) uses correct ChannelHandlerContext now
[#982] [#977] [#858] Allow to transfer the content a ChannelHandlers inbound/outbound buffer on removal/replacement

This changes the behavior of the ChannelPipeline.remove(..) and ChannelPipeline.replace(..) methods in that way
that after invocation it is not possible anymore to access any data in the inbound or outbound buffer. This is
because it empty it now to prevent side-effects. If a user want to preserve the content and forward it to the
next handler in the pipeline it is adviced to use one of the new methods which where introduced.

 - ChannelPipeline.removeAndForward(..)
 - ChannelPipeline.replaceAndForward(..)
[#988] Fix typo