Socket not closed on exception-driven connection failure

[tsegismont]

When a connection handles a failure (e.g. decoding exception), the underlying Netty channel is not closed unless the application explicitly calls connection.close().

This leaks socket file descriptors and Netty resources until the application closes the connection or the Vertx instance shuts down.