fix(tls): exit handshake loop on NOT_HANDSHAKING to kill latent busy-spin

The NEED_TASK branch reads sslEngine.getHandshakeStatus(), which per the JSSE
contract never returns FINISHED -- it returns NOT_HANDSHAKING once the handshake
completes. If a delegated task were the terminal handshake step, the loop would
land on NOT_HANDSHAKING, match no switch case, and busy-spin at 100% CPU with no
deadline escape. Exit the loop on NOT_HANDSHAKING (a completed handshake) as well
as FINISHED, closing this latent/provider-dependent spin path.

Author: bluestreak01

core/src/main/java/io/questdb/client/network/JavaTlsClientSocket.java

@@ -514,7 +514,12 @@ private int readFromSocket() {
      */
     private void runHandshake(SocketReadinessWaiter waiter) throws SSLException, TlsSessionInitFailedException {
         SSLEngineResult.HandshakeStatus handshakeStatus = sslEngine.getHandshakeStatus();
-        while (handshakeStatus != SSLEngineResult.HandshakeStatus.FINISHED) {
+        // Exit on NOT_HANDSHAKING as well as FINISHED: getHandshakeStatus() (used by the NEED_TASK
+        // branch) never returns FINISHED per the JSSE contract -- it returns NOT_HANDSHAKING once the
+        // handshake completes. Without this, a delegated task that is the terminal step would leave the
+        // loop on NOT_HANDSHAKING, match no case, and busy-spin forever with no deadline escape.
+        while (handshakeStatus != SSLEngineResult.HandshakeStatus.FINISHED
+                && handshakeStatus != SSLEngineResult.HandshakeStatus.NOT_HANDSHAKING) {
             switch (handshakeStatus) {
                 case NEED_TASK:
                     Runnable task;