Fix client artifact ID in CI version overrides

The client module's artifactId was renamed from "client" to
"questdb-client", but the CI pipeline's versions:use-dep-version
steps still filtered on org.questdb:client. The filter never
matched, so QuestDB's build tried to fetch the unreleased
questdb-client:1.0.2-SNAPSHOT from Maven Central instead of
using the locally installed 9.9.9 jar.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: mtopolnik

ci/run_tests_pipeline.yaml

@@ -95,21 +95,21 @@ stages:
               mavenPOMFile: "questdb/core/pom.xml"
               jdkVersionOption: "default"
               goals: "versions:use-dep-version"
-              options: "-Dincludes=org.questdb:client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
+              options: "-Dincludes=org.questdb:questdb-client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
           - task: Maven@3
             displayName: "Update QuestDB client version: benchmarks"
             inputs:
               mavenPOMFile: "questdb/benchmarks/pom.xml"
               jdkVersionOption: "default"
               goals: "versions:use-dep-version"
-              options: "-Dincludes=org.questdb:client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
+              options: "-Dincludes=org.questdb:questdb-client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
           - task: Maven@3
             displayName: "Update QuestDB client version: utils"
             inputs:
               mavenPOMFile: "questdb/utils/pom.xml"
               jdkVersionOption: "default"
               goals: "versions:use-dep-version"
-              options: "-Dincludes=org.questdb:client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
+              options: "-Dincludes=org.questdb:questdb-client -DdepVersion=9.9.9 -DforceVersion=true --batch-mode"
           - task: Maven@3
             displayName: "Compile QuestDB"
             inputs: