fix: worker-poll tasks shouldn't block main loop (#7427)

Fixes a call to execute a task on the worker pool that still may block main event-loop
execution. See #7358 for more information.

Reviewers: @guozhangwang

ksqldb-rest-app/src/main/java/io/confluent/ksql/api/auth/JaasAuthProvider.java

@@ -96,6 +96,7 @@ public void authenticate(
 
     server.getWorkerExecutor().executeBlocking(
         p -> getUser(contextName, username, password, allowedRoles, p),
+        false,
         resultHandler
     );
   }

ksqldb-rest-app/src/main/java/io/confluent/ksql/api/auth/KsqlAuthorizationProviderHandler.java

@@ -57,6 +57,7 @@ public void handle(final RoutingContext routingContext) {
 
     workerExecutor.<Void>executeBlocking(
         promise -> authorize(promise, routingContext),
+        false,
         ar -> handleAuthorizeResult(ar, routingContext));
   }
 

ksqldb-rest-app/src/test/java/io/confluent/ksql/api/auth/JaasAuthProviderTest.java

@@ -19,6 +19,7 @@
 import static org.hamcrest.Matchers.instanceOf;
 import static org.hamcrest.Matchers.is;
 import static org.mockito.ArgumentMatchers.any;
+import static org.mockito.ArgumentMatchers.eq;
 import static org.mockito.Mockito.doAnswer;
 import static org.mockito.Mockito.mock;
 import static org.mockito.Mockito.verify;
@@ -253,11 +254,11 @@ private void handleAsyncExecution() {
     when(server.getWorkerExecutor()).thenReturn(worker);
     doAnswer(invocation -> {
       final Handler<Promise<User>> blockingCodeHandler = invocation.getArgument(0);
-      final Handler<AsyncResult<User>> resultHandler = invocation.getArgument(1);
+      final Handler<AsyncResult<User>> resultHandler = invocation.getArgument(2);
       final Promise<User> promise = Promise.promise();
       promise.future().onComplete(resultHandler);
       blockingCodeHandler.handle(promise);
       return null;
-    }).when(worker).executeBlocking(any(), any());
+    }).when(worker).executeBlocking(any(), eq(false), any());
   }
 }