Add Devfile for Quarkus with Java 21

[datho7561]

Which area this feature is related to?

/area ci
/area api
/area library
/area registry
/area alizer
/area devworkspace
/area integration-tests
/area test-automation
/area releng
/area documentation
/area landing-page

Which functionality do you think we should add?

It would be nice to have a Devfile that supports running Java 21 Quarkus applications. If a user tries to use odo with a Java 21, the recommended Devfile doesn't work, because it comes with Java 17 and Java 21 is required.

Why is this needed? Is your feature request related to a problem?

Java 21 is the latest LTS release of Java. It has been out for a few months. People who are creating new Java projects are likely using Java 21 in order to use the exciting new features.

Detailed description:

Describe the solution you'd like

A new Devfile for Quarkus with Java 21.

The key changes that you need to make to the Java 17 Quarkus Devfile in order to get it to work with Java 21 are:

• Change the container image to registry.access.redhat.com/ubi9/openjdk-21:1.18-4
• Replace the query string for the example project to use Java 21: &j=17 ==> &j=21
• Change any documentation (names, descriptions) from Java 17 to Java 21

Describe alternatives you've considered

The user could modify the existing Devfile themselves to get it to work, but this requires the user to know a lot about Devfiles, since you need to know that you need to replace container image. This is also not a good solution because this is the Devfile that is recommended to the user if they want to add a Devfile to an existing Java 21 Quarkus project, so they would expect that no modification is required.

Additional context

[michael-valdron]

There is a PR open for this issue: devfile/registry#370

I'll link this issue in the PR description and assign the author @vinokurig.