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.
What do you plan on doing in this case?  I believe priority is more useful for controlling sending flow (in the outbound flow controller).  At this level you should be free to send away ... if it gets backed up, the flow controller will start managing the outbound flow based on stream priority.

We probably should add a mechanism to let the upper levels know that the outbound flow controller is getting backed up, but that's a separate topic/issue.