Update Jib base image to eclipse-temurin:21-alpine-3.22

[jreynard-code]

No description provided.

[sjoubert]

Version 3.22 seems to be the latest version, I'm a bit surprised it's not using it be default (aka this should currently not be an "upgrade"):

• Maybe the docker image pull is not configured with the --pull option that's perhaps the reason it was not using 3.22 implicitly. Do we want to fix the version or instead make sure to use the latest by trying to force the image pull?
• On docker hub I only see the last 3 versions (3.20, 3.21 and 3.22), does that mean by fixing the version we risk having it break in the future when they remove it? I don't know the schedule release of these images, it may be a while until this happens.

Anyway, the question of fixing dependency version is always a tricky one and depends on the usage and context, so I don't know which approach is best here.

[jreynard-code]

Version 3.22 seems to be the latest version, I'm a bit surprised it's not using it be default (aka this should currently not be an "upgrade"):

• Maybe the docker image pull is not configured with the --pull option that's perhaps the reason it was not using 3.22 implicitly. Do we want to fix the version or instead make sure to use the latest by trying to force the image pull?
• On docker hub I only see the last 3 versions (3.20, 3.21 and 3.22), does that mean by fixing the version we risk having it break in the future when they remove it? I don't know the schedule release of these images, it may be a while until this happens.

Anyway, the question of fixing dependency version is always a tricky one and depends on the usage and context, so I don't know which approach is best here.

Good catch ;) I compare the sha256 and they are identical, I was too urged yesterday afternoon ;)

I close the PR ;)