[CI] Add pre-release testing for Quarkus with fixed JDK version and locally installed maven artifact for graal-sdk

[jerboaa]

Description

In order to avoid oracle#6831 in the future we should change our CI or add new testing which compiles Quarkus with a fixed (older JDK). This testing shall use a locally installed maven artifact from the mandrel build org.graalvm.sdk:graal-sdk as built like so:

$ cd sdk
$ mx build
$ mx --suite sdk maven-deploy --suppress-javadoc

Such a CI workflow shall parameterize on the JDK version to use for quarkus (e.g. JDK 11 for Quarkus 3.2) as it's expected to change from one release cycle to the next.

[jerboaa]

graalvm/mandrel-packaging#354 adds support to the mandrel build to deploy to the local maven repository. After that has shipped the CI workflow should be like so:

1. Build mandrel with option '--maven-deploy-local' and recursively erasing
   '~/.m2/repository/org/graalvm/' before.
3. After step 1 the maven repo would only contain the locally built org.graalvm.* artefacts.
   The maven version for those would be in file `$GRAALVM_HOME/.maven-version`
5. Get JDK 11
6. Point at the JDK 11 install with JAVA_HOME and build quarkus, passing -Dgraal-sdk.version=$(cat $GRAALVM_HOME/.maven-version)

The idea would be that such a workflow would fail prior oracle#6949 and pass after it.

[github-actions]

This issue appears to be stale because it has been open 30 days with no activity. This issue will be closed in 7 days unless Stale label is removed, a new comment is made, or not-Stale label is added.

[jerboaa]

Successful merge of #565 should complete this work.