Fixing bugs in HTTP/2 pipeline exception handling

Motivation:

HTTP/2 codec does not properly test exception passed to
exceptionCaught() for instanceof Http2Exception (since the exception
will always be wrapped in a PipelineException), so it will never
properly handle Http2Exceptions in the pipeline.

Also if any streams are present, the connection close logic will execute
twice when a pipeline exception. This is because the exception logic
calls ctx.close() which then triggers the handleInActive() logic to
execute.  This clears all of the remaining streams and then attempts to
run the closeListener logic (which has already been run).

Modifications:

Changed exceptionCaught logic to properly extract Http2Exception from
the PipelineException.  Also added logic to the closeListener so that is
only run once.

Added a test for verifying that a pipeline exception closes the
connection.

Result:

Exception handling logic is tidied up.
I understand you have an immediate need for this but I would also like to make sure it makes sense in the general case too. I agree that re-architecture seems to be beyond the scope of this PR but it seems like we are re-architecting anyways by re-introducing classes that were explicitly removed.  Does just limiting this PR to include the fixes for the exception bugs (including `Http2LifecycleManager.java`) and opening a followup PR to address the architecture concerns work?

For example there is an unlisted option 3 where we allow the input/output layers to be combined more easily/intuitively (today input is `Http2FrameListener ` and output is `Http2OutboundConnectionAdapter`) so we can achieve extension more easily/cleanly.