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 am running into a null pointer exception here because cause exists but `getMessage()` returns null.  We should protect against this case.  The exception type is `java.nio.channels.ClosedChannelException`

> java.lang.NullPointerException
	at java.util.regex.Matcher.getTextLength(Matcher.java:1234)
	at java.util.regex.Matcher.reset(Matcher.java:308)
	at java.util.regex.Matcher.<init>(Matcher.java:228)
	at java.util.regex.Pattern.matcher(Pattern.java:1088)
	at java.util.Formatter.parse(Formatter.java:2515)
	at java.util.Formatter.format(Formatter.java:2469)
	at java.util.Formatter.format(Formatter.java:2423)
	at java.lang.String.format(String.java:2790)
	at io.netty.handler.codec.http2.Http2Exception.format(Http2Exception.java:45)
	at io.netty.handler.codec.http2.Http2CodecUtil.toHttp2Exception(Http2CodecUtil.java:142)
	at io.netty.handler.codec.http2.Http2OutboundConnectionAdapter$1.operationComplete(Http2OutboundConnectionAdapter.java:82)