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.
The plan is to be able to provide translation for all Http/2 frame events to FullHttpMessage objects.  This may be useful for a simplistic client which wants to know that the server is talking, and also have context into what the connection/server state is.  The intention is for this to be largely informational and not for the client to re-implement flow control, but if the information is accurate the consumer could do what they want with it (log it, observe behavior, some other process,...).

The longer term plan I had in mind is as follows (to be resolved with the other opened issues)...

Support 2 modes of operation:
1. Forward HTTP/2 headers/data only
2. Forward all HTTP/2 events

This will be controlled by having a base class (inheriting from Http2FrameObserver) provide the data/header processing, and then have a class inherit from this to provide all the rest of the Http/2 frame translations.  The `InboundHttp2ToHttpAdapter` will create the correct instance at construction time and delegate all events to this instance.