Java CI: reduce the risk of failures from Maven Central rate-limiting

[jameslamb]

Description

Across a few projects, we've been seeing errors like this intermittently for at least the last 2 months:

Error: Plugin org.apache.maven.plugins:maven-jar-plugin:3.0.2 or one of its dependencies could not be resolved:
Error: The following artifacts could not be resolved: org.apache.maven.plugins:maven-jar-plugin:pom:3.0.2 (absent): Could not transfer artifact org.apache.maven.plugins:maven-jar-plugin:pom:3.0.2 from/to central (https://repo.maven.apache.org/maven2): status code: 429, reason phrase: Too Many Requests (429)

That's been observed in:

• cuDF (Use google cloud read-only Maven Central mirror cudf#22875)
• cuVS (fix(java): use Maven mirror, remove unnecessary plugins, other CI-stability improvements NVIDIA/cuvs#2253)
• cuVS-lucene (builds failing: "Failed to read artifact descriptor for org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.7" NVIDIA/cuvs-lucene#145)
• kvikio (https://github.com/rapidsai/kvikio/actions/runs/28007417984/job/82961513523)

This tracks the work of addressing that issue.

Benefits of this work

• stabilizes Java CI for RAPIDS projects
• standardizes some Java packaging / testing details across RAPIDS repos

Acceptance Criteria

• Java CI is relying on Maven Central as little as possible

Approach

Copy the changes from NVIDIA/cuvs#2253

This affects all projects using Maven in CI on NVIDIA's self-hosted GitHub Actions runners (GitHub search)

• cudf
  • using GCS mirror (Use google cloud read-only Maven Central mirror cudf#22875)
  • other changes (java: use GCS mirror for Maven Central, other small changes cudf#22969)
• cuvs (fix(java): use Maven mirror, remove unnecessary plugins, other CI-stability improvements NVIDIA/cuvs#2253)
• cuvs-lucene (use GCS mirror for Maven, fix benchmarks version, other small changes NVIDIA/cuvs-lucene#166)
• kvikio (java: use GCS mirror for Maven, other small changes kvikio#992)

Notes

N/A

[jameslamb]

This is done.