chore: factorize JDK specification to docker bakefile (linux) / compose file (windows)

[dduportal]

Blocked by #414

This pull request aims at factorizing the image definitions (Dockerfiles) to avoid duplicating code between JDK versions.

Until now, changing an element in any of the images which have both JDK11 and JDK17 definitions were subject to a risk of shift if the 2nd image is forgotten.

How does it work?

• The directories 11/ and 17/, representing the major JDK version, are removed
• There is only 1 directory per operating system at the root of the repository
  • Please note that bullseye is renamed to debian during this change for the following reasons:
    • Stay homogeneous with https://github.com/jenkinsci/docker and https://github.com/jenkinsci/docker-inbound-agent
    • The distribution codename is already specified in the Dockerfile as part of the FROM instruction and is subject to change in the futures
    • Changing the directory name breaks the GitHub permalinks: I'm proposing to tie both changes as this PR also breaks the GitHub permalinks
• The JDK version is passed through build arguments
  • The Dockerfiles do have a default version defined to ensure it's buildable "as it" (e.g. without Docker BuildX and its bake file). The proposed convention is to set it to the "most recent LTS JDK of the images"..
• Archlinux only exists for JDK11. It's updated to follow the same rules, and adding a JDK17 version should be another PR (and will be needed AND a good test for this refactoring).

TODO:

• Factorize Linux images
• Factorize Windows images
• Fix Updatecli manifests for tracking JDK versions - chore(updatecli) fix JDK version tracking - fixup of #409 #417
• Open an issue or a PR for Archlinux JDK17 - Decide the future of the Archlinux image: either add "Archlinux JDK17" or remove "Archlinux JDK11" #422

Testing done

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

[timja]

any way to see if anyone actually uses Archlinux?

[dduportal]

any way to see if anyone actually uses Archlinux?

The DockerHub download stats would be useful there

[dduportal]

Rebased on top of #414 : let's see if it works as expected

[MarkEWaite]

Looks very good to me.

[dduportal]

Please note that the following fixup changes were needed after this PR:

• chore(updatecli) fix JDK version tracking - fixup of #409 #417
• chore: fix Dockerfile location on the last items - fixup of #409 #420
• e4c81a8