Release & Package Processes: "one container to rule them all"

[dduportal]

As per https://issues.jenkins.io/browse/JENKINS-67474, we are facing issues with the current Kubernetes plugin version (1.31.x line).

Feature Request

The only viable solution as for today, if we keep using Kubernetes agents, is to use "single-container pod", where we defined only 1 container named jnlp, based on an image that inherits (or behaves like) jenkins/inbound-agent AND with all the tools required.

We have 3 cases to handle on the master branch:

• Linux Packaging process (challenge is to be able to install ALL the packaging tools for Debian, Redhat, Suse, etc.)
• Windows Packaging Process (challenge is to build and maintain an image for this case as we use existing external images as for today)
• Linux Release process (challenge is to use a prebuilt image that is compliant with our system)

There is also cherry-picking to be done to the following addition branches:

• TODO (I need help on this @timja )

[dduportal]

Linux Packaging process has been solved by the following changes:

• fix: switch linux packaging to single-container JNLP with dduportal image #197 (validate initial behavior)
  -Bump package image to jenkinsciinfra/packaging:2.0.0 #198 (switch to the jenkinsciinfra/packaging:2.0.0) image

=> it worked flawlessly with the image that embed azure CLI, JDK Maven, and all the exsiting tools.

[dduportal]

• Linux release process is constrained by Execute Release Process with JDK11 #199
• Windows packaging process is constrained by Switch Windows Packaging Envrionement from Windows Server Core 18.09 to Windows Server Core LTSC~2019~ 2022 #200

[dduportal]

• PR Feat: one container to rule them all #203 merged to have release-linux on "single container".
• WiP on Wip: add Windows image docker-packaging#23 to have a windows version of the docker-packaging image (thanks to @smerle33 whom fixed infra.ci's VM Windows agent ❤️ ). It would solve Switch Windows Packaging Envrionement from Windows Server Core 18.09 to Windows Server Core LTSC~2019~ 2022 #200 + this issue.