fix: mitigate problem with ChainAuthHandler

A problem with the ChainAuthHandler was introduced in vert.x version
4.5.6. To mitigate the issue, we do not use the vert.x
ChainAuthHandler when only one AuthenticationHandler is used. The
problem still exists when more than one AuthenticationHandler is used.

vert-x3/vertx-web#2611

src/main/java/io/neonbee/internal/handler/ChainAuthHandler.java

@@ -29,16 +29,16 @@ static ChainAuthHandler create(Vertx vertx, List<AuthHandlerConfig> authChainCon
             return NOOP_AUTHENTICATION_HANDLER;
         }
 
+        List<AuthenticationHandler> authHandlers = authChainConfig.stream()
+                .map(config -> config.createAuthHandler(vertx)).toList();
+
+        if (authHandlers.size() == 1) {
+            AuthenticationHandler authenticationHandler = authHandlers.get(0);
+            return authenticationHandler::handle;
+        }
+
         io.vertx.ext.web.handler.ChainAuthHandler chainAuthHandler = io.vertx.ext.web.handler.ChainAuthHandler.any();
-        List<AuthenticationHandler> authHandlers =
-                authChainConfig.stream().map(config -> config.createAuthHandler(vertx)).toList();
         authHandlers.forEach(chainAuthHandler::add);
-
-        return new ChainAuthHandler() {
-            @Override
-            public void handle(RoutingContext event) {
-                chainAuthHandler.handle(event);
-            }
-        };
+        return chainAuthHandler::handle;
     }
 }