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.
I appears that the end of headers is being processed upstream [here](https://github.com/netty/netty/blob/master/codec-http2/src/main/java/io/netty/handler/codec/http2/DefaultHttp2FrameReader.java#L412) and [here](https://github.com/netty/netty/blob/master/codec-http2/src/main/java/io/netty/handler/codec/http2/DefaultHttp2FrameReader.java#L438) and the `onHeadersRead` is not invoked until this flag is detected.  It is not clear in the spec definition for how the END_HEADERS flag should be set for steps 1 and 2.  If the END_HEADERS flag is not set on the first informational status code set of headers then I don't think we can continue queuing these events in `DefaultHttp2FrameReader`.  I opened an issue to get clarification on the message flow on the HTTP/2 spec repo https://github.com/http2/http2-spec/issues/597.  If the END_HEADERS flag is set for each step then I can simplify my code (which is also queuing up headers).