Use JDK25 for our Jenkins controllers

[dduportal]

Service(s)

cert.ci.jenkins.io, ci.jenkins.io, infra.ci.jenkins.io, release.ci.jenkins.io, trusted.ci.jenkins.io, weekly.ci.jenkins.io

Summary

JDK25 is the current Java LTS.
We should run our Jenkins controller and agents using it instead of JDK21:

• For obvious platform health (keeping it up to date)
• For supporting the effort of Jenkins community to validate Jenkins ecosystem on JDK25

For historical reference, the migration JDK17 -> JDK21 of our controllers is a subset of #4120

Scope:

• This issue is only about the JDK runtime used to execute our Jenkins controllers and their agents. Nothing related to the JDK versions used in builds and pipelines.
• We have the following controllers to migrate from JDK21 to JDK25:
  • infra.ci.jenkins.io (based on weekly line) - feat! Switch to JDK25 docker-jenkins-infraci#263
  • weekly.ci.jenkins.io (based on weekly line) - feat! Switch to JDK25 docker-jenkins-weeklyci#1884
  • trusted.ci.jenkins.io (based on LTS line) - feat(trusted.ci.jenkins.io, cert.ci.jenkins.io and aws.ci.jenkins.io)! Switch to JDK25 jenkins-infra#4730
  • cert.ci.jenkins.io (based on LTS line) - feat(trusted.ci.jenkins.io, cert.ci.jenkins.io and aws.ci.jenkins.io)! Switch to JDK25 jenkins-infra#4730
  • release.ci.jenkins.io (based on LTS line) - feat! Switch to JDK25 docker-jenkins-lts#1068
  • ci.jenkins.io (based on LTS line) - feat(trusted.ci.jenkins.io, cert.ci.jenkins.io and aws.ci.jenkins.io)! Switch to JDK25 jenkins-infra#4730
• We have the following agents:
  • Permanent agents (SSH):
    • s390x.jenkins.io (ci.jenkins.io)
    • trusted.agent.jenkins.io (trusted.ci.jenkins.io)
  • EC2 agents (ci.jenkins.io): Ubuntu and Windows VMs
  • Azure VM agents (infra.ci.jenkins.io, trusted.ci.jenkins.io, cert.ci.jenkins.io): Ubuntu and Windows VMs
  • Kubernetes agents (ci.jenkins.io, infra.ci.jenkins.io, release.ci.jenkins.io): Ubuntu containers

Reproduction steps

No response