Document support for java 17 in generated projects - Codestarts

• Release notes for the Red Hat build of Quarkus 2.7
• Deploying your Quarkus applications to OpenShift

SME: manderse@redhat.com

The Elektra release will add the capability of generating projects based on Java 17.
In 2.2.5, the Quarkus tooling (Maven Plugin, CLI) only allows generating projects based on Java 11. Java 17 is supported but the projects must be configured to use Java 17 manually by updating the project POM and Dockerfiles, etc.
In Elektra the manual re-configuration will not be necessary in projects generated using Quarkus developer tools.
According to information from Thomas, code.quarkus.redhat.com will be an exception to this, because it will not support generating projects based on Java 17 in Elektra.

Docs impact:

OpenShift Guide
As a result, we'll need to update the section of the OpenShift guide that describes manually setting the Java version.
We can repurpose this section to describe how to manually set the Java version in a Quarkus project (This would be somewhat useful for modifying project created using code.quarkus.redhat.com)

Release Notes
Similarly to what we did when we introduced Java 17 support in 2.2.5, we should document this change in the Release notes under New and Changed Features.