Fix false positive unexpected connection close

Motivation:
The connection could be incorrectly detected as
unexpectedly closed due to a race condition where the exit message was
sent before updating the state to `ST_CLOSING`.

Modifications:
Ensured state update to `ST_CLOSING` happens before
sending the exit message.

Result:
State update to `ST_CLOSING` happens before sending the exit
message, preventing false positive unexpected close detections.
resolves #275

Author: jchrys

r2dbc-mysql/src/main/java/io/asyncer/r2dbc/mysql/client/ReactorNettyClient.java

@@ -131,6 +131,14 @@ final class ReactorNettyClient implements Client {
                     logger.debug("Request: {}", message);
                 }
 
+                if (message == ExitMessage.INSTANCE) {
+                    if (STATE_UPDATER.compareAndSet(this, ST_CONNECTED, ST_CLOSING)) {
+                        logger.debug("Exit message sent");
+                    } else {
+                        logger.debug("Exit message sent (duplicated / connection already closed)");
+                    }
+                }
+
                 if (message.isSequenceReset()) {
                     resetSequence(connection);
                 }
@@ -213,15 +221,8 @@ public Mono<Void> close() {
 
             requestQueue.submit(RequestTask.wrap(sink, Mono.fromRunnable(() -> {
                 Sinks.EmitResult result = requests.tryEmitNext(ExitMessage.INSTANCE);
-
                 if (result != Sinks.EmitResult.OK) {
                     logger.error("Exit message sending failed due to {}, force closing", result);
-                } else {
-                    if (STATE_UPDATER.compareAndSet(this, ST_CONNECTED, ST_CLOSING)) {
-                        logger.debug("Exit message sent");
-                    } else {
-                        logger.debug("Exit message sent (duplicated / connection already closed)");
-                    }
                 }
             })));
         }).flatMap(Function.identity()).onErrorResume(e -> {