Upgrading to HTTP/2 draft 14 HTTP/1.x message flow

Motivation:

HTTP/2 draft 14 came out a couple of weeks ago and we need to keep up
with the spec.

Modifications:

-Allow informational type messages to be sent up the pipeline immediatley.
-Corrections to HttpObject comparitors to support test cases
-New test cases to support sending headers immediatley
-Bug fixes cleaned up to ensure the message flow is terminated properly

Result:
Netty HTTP/2 to HTTP/1.x translation layer will support the HTTP/2 draft message flow.
No specific use case, but for example would introducing a read timeout require extending the HTTP/2 codec and handling each event?  This would just provide an option for a simplified pipeline and my assumption is it may be useful for client code.  I agree that option 1 would be the default either way.

If the user wanted HTTP objects for data but also wanted to get other HTTP/2 events would the use case be to extend `InboundHttp2ToHttpAdapter`?