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 think there are just 2 places where the request/response are considered:
1. Determine if the message must be forwarded up the pipeline immediately (`mustSendImmediately`).
2. After (1) then we may need to preserve the headers in-case headers can be received after this point.  This is what the `postImmediateSendMessageCopy` is intended for.

These two steps are related but also decoupled now.  Having these methods decouples the request/response logic from the core algorithm of handing message flow.  Some of this may be defined by the spec the behavior is generic enough where it *may* also be extensible in the future (I don't have a concrete example for this now).  I think I like having the request/response processing decoupled from the main algorithmic flow as it keeps things decoupled and separates concerns a bit.