chore(dependencies): Use updatecli to track JDK 11, 17 and 21

[gounthar]

After @MarkEWaite's comment on PR #1707 (and the subsequent PR #1710), I am proposing three manifests to track the JDK versions. Specifically, I have created three updatecli manifests for JDK 11, 17, and 21.

This shouldn't be merged work until #1710 and #1712 are merged, and updatecli gets upgraded to version 0.61.0.

Testing done

updatecli diff --config ./updatecli/updatecli.d/jdk11.yaml --values ./updatecli/
values.github-action.yaml --debug
updatecli diff --config ./updatecli/updatecli.d/jdk17.yaml --values ./updatecli/
values.github-action.yaml --debug
updatecli diff --config ./updatecli/updatecli.d/jdk21.yaml --values ./updatecli/
values.github-action.yaml --debug

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[gounthar]

Last build failed, but I'm not so sure it's my fault:

ERROR: failed to solve: process "/bin/sh -c curl -fsSL ${JENKINS_URL} -o /usr/share/jenkins/jenkins.war   && echo \"${JENKINS_SHA}  /usr/share/jenkins/jenkins.war\" >/tmp/jenkins_sha   && sha256sum -c --strict /tmp/jenkins_sha   && rm -f /tmp/jenkins_sha" did not complete successfully: exit code: 22
[1299](https://ci.jenkins.io/job/Packaging/job/docker/job/PR-1711/11/pipeline-console/?start-byte=296974&selected-node=858#log-1299)
script returned exit code 1

[dduportal]

The updatecli manifests look really good.

But we have to, first, work on #1710 to avoid PR with double quotes 😅

Blocking until #1710 is merged and it is rebased (with conflict merges) here

[dduportal]

• Don't forget chore(dependencies): Preliminary work to integrate updatecli. #1710 (comment) (removing dependabot JDK tracking in favor of updatecli)
• Looks like we forgot to update the Windows dockerfiles in chore(dependencies): Preliminary work to integrate updatecli. #1710 : worth another (tiny) PR if we want updatecli to work properly in this PR

[gounthar]

Thank you Damien.

• Looks like we forgot to update the Windows dockerfiles in chore(dependencies): Preliminary work to integrate updatecli. #1710 : worth another (tiny) PR if we want updatecli to work properly in this PR

Strangely, I had done it in #1711...
That is corrected through #1720 .

[gounthar]

Following this comment, I tried to remove the dependabot work about Java.

[dduportal]

One last thing: as we discussed last week let's roll back the updatecli manifest to use ARG instead of FROM.

Rationale is that, even if the initial proposal to use FROM looked simpler, we want to use the Docker Bake to specify the JAVA_VERSION so ARG is mandatory.
The idea is to, like for agents, to Remove the ARG default value.

[dduportal]

Run Summary
===========
Pipeline(s) run:
  * Changed:	0
  * Failed:	0
  * Skipped:	0
  * Succeeded:	4
  * Total:	4

Nice work 👏