JDK 22 CI build

[szpak]

This PR adds JDK 22 CI build.

I don't see a good reason to build with both 21 LTS and 22, so the former is replaced by the later.

As a bonus, I also improved the visibility in GitHub Actions UI, the order of matrix variables has been changed (I might move it to a separate PR, if desired).

Before (JDK version and Groovy variant are not visible in the failing builds):

After:

[szpak]

@leonard84 It seems you need to click somewhere in the project settings to choose the new "mandatory checks".

[Vampire]

It seems you need to click somewhere in the project settings to choose the new "mandatory checks".

After it was decided to merge the PR, yep.
Otherwise all other PRs will miss required checks until this eventually got merged maybe.
But don't worry, he can merge the PR even with the required checks missing due to the rename. :-)

I don't see a good reason to build with both 21 LTS and 22, so the former is replaced by the later.

Well, 21 is LTS 22 is latest.
Imho that might well be reason enough to build for both.

[szpak]

After it was decided to merge the PR, yep.
Otherwise all other PRs will miss required checks until this eventually got merged maybe.

Sure. That was my intention.

Well, 21 is LTS 22 is latest.
Imho that might well be reason enough to build for both.

We have already a large number of builds. Initially, I was thinking about limiting a number of builds with "intermediate" versions. However, in the end, the two extra build (21 with 3.0 and 4.0) would probably not be a big problem.

[szpak]

the two extra build (21 with 3.0 and 4.0) would probably not be a big problem.

Sometimes 4 builds - for a push and for a PR (I will start making my branches in my fork).

[Vampire]

LGTM, but Leonard should have the last word and especially merge it to then adapt the required checks.

[szpak]

@leonard84 Any more suggestions here?