fix(test): use Java 8 try-with-resources in QuestDBServerRecoveryTest

try (server) on an effectively-final existing variable is Java 9+ syntax
(JEP 213) and fails the JDK 8 test-compile (the source-of-truth target)
with -source 1.8, breaking the build-jdk8 CI job and the release build
before any test runs. Inline the resource construction into the
try-with-resources declaration, which is valid on Java 8 and keeps the
server variable name used throughout the body.

Author: bluestreak01

core/src/test/java/io/questdb/client/test/QuestDBServerRecoveryTest.java

@@ -52,9 +52,8 @@ public void testFacadeStartsWhileServerDownThenWritesAndReaderConnectsOnRecovery
         // completes, so the server is effectively "down". It serves ingest ACK
         // on the write path and a SERVER_INFO frame on the read path -- the read
         // path is gated so the ingest connection's ACK stream is never disturbed.
-        TestWebSocketServer server = new TestWebSocketServer(new TestWebSocketServer.WebSocketServerHandler() {
-        });
-        try (server) {
+        try (TestWebSocketServer server = new TestWebSocketServer(new TestWebSocketServer.WebSocketServerHandler() {
+        })) {
             server.setSendServerInfo(true); // the egress client's connect() waits for SERVER_INFO
             // One cluster config drives both pools:
             // lazy_connect=true expands to exactly this resilience: the ingest