Fix `cleanResponses` must handle cleaning up cancelled future (nats-i…

…o#1218)

* Fix `cleanResponses` must handle cleaning up cancelled future

If a future would be cancelled outside of `cleanResponses`, calling `future.get()` would throw a `CancellationException`.

This exception was not caught, breaking future cleanup.

Signed-off-by: Maurice van Veen <[email protected]>

* Catch Throwable

Signed-off-by: Maurice van Veen <[email protected]>

---------

Signed-off-by: Maurice van Veen <[email protected]>

Remove redundant `writer.flushBuffer()` call (nats-io#1207)

When doing a request through `requestFutureInternal` we'd publish the message into the outgoing write queue, and immediately after call `writer.flushBuffer()`.

Due to the message needing to go through the outgoing message queue, which takes a small amount of time, the `flushBuffer` would be done first and before our message got written to the `dataPort`.

Removing the call to `writer.flushBuffer()` since it doesn't actually flush our message/request.

Signed-off-by: Maurice van Veen <[email protected]>

[Flapper] Reconnect test fix (nats-io#1189)

Augmented force reconnect (nats-io#1165)

Improve socket close behavior

Remove duplicate reconnect event (nats-io#1151)

Start 2.18.0 (nats-io#1139)

Remove rethrowable runtime exception during connection (nats-io#1137)

Watch test 284 (nats-io#1117)

Graalvm readme touch-up (nats-io#1115)