fix(client): allow token to coexist with egress basic-auth password in one cluster config

A single QuestDB.connect() string drives both the ingest and the query
pools: the egress side authenticates with username=/password= while the
ingest side may use token=. The ingest parser's auth conflict is only its
own key pair (token + user); a password that belongs to the egress pair is
no longer rejected.

Author: bluestreak01

core/src/main/java/io/questdb/client/Sender.java

@@ -39,6 +39,7 @@
 import io.questdb.client.cutlass.qwp.client.sf.cursor.CursorSendEngine;
 import io.questdb.client.cutlass.qwp.client.sf.cursor.CursorWebSocketSendLoop;
 import io.questdb.client.impl.ConfStringParser;
+import io.questdb.client.impl.ConfigSchema;
 import io.questdb.client.impl.ConfigString;
 import io.questdb.client.impl.ConfigView;
 import io.questdb.client.network.NetworkFacade;
@@ -3741,7 +3742,7 @@ static void validateWsConfig(ConfigView view, boolean tls) {
             if ((user == null) != (password == null)) {
                 throw new IllegalArgumentException("username and password must be provided together");
             }
-            if (token != null && (user != null || password != null)) {
+            if (token != null && user != null) {
                 throw new IllegalArgumentException("cannot use both token and username/password authentication");
             }
             String tlsVerify = view.getStr("tls_verify");