Use Maven Central metadata for version resolution, add CodeQL dispatch trigger

- Switch from GitHub API to Maven Central maven-metadata.xml to resolve
  the latest Maven 3.x version (avoids rate limiting on unauthenticated requests)
- Filter for stable 3.x releases only (no alpha/beta/rc, no Maven 4.x)
- Add workflow_dispatch trigger to CodeQL workflow for manual runs

Author: tortmayr

.github/workflows/codeql-analysis.yml

@@ -14,6 +14,7 @@ defaults:
   run:
     working-directory: ./client
 on:
+  workflow_dispatch:
   schedule:
     - cron: '19 3 * * 5'
 

Jenkinsfile

@@ -67,7 +67,7 @@ pipeline {
             steps {
                 container('ci') {
                     sh '''
-                        MAVEN_VERSION=$(curl -sf "https://api.github.com/repos/apache/maven/releases/latest" | grep '"tag_name"' | sed 's/.*"maven-\\([^"]*\\)".*/\\1/')
+                        MAVEN_VERSION=$(curl -sf "https://repo1.maven.org/maven2/org/apache/maven/apache-maven/maven-metadata.xml" | awk -F '[<>]' '/<version>3\\.[0-9]+\\.[0-9]+</{v=$3} END{print v}')
                         curl -o maven.tar.gz -L "https://dlcdn.apache.org/maven/maven-3/${MAVEN_VERSION}/binaries/apache-maven-${MAVEN_VERSION}-bin.tar.gz"
                         tar -xzf maven.tar.gz -C ${WORKSPACE}
                         rm -f maven.tar.gz