Use major.minor part of GraalVM version in documentation

[zakkak]

Users should always be encouraged to use the latest release of a feature release, i.e., prefer 22.3.1 over 22.3.0.

Micro releases (called CPU releases in GraalVM) should not break compatibility, instead they should only bring bug fixes. As a result they should be considered safe to use.

This change also enables referencing the version specific graalvm docs as discussed in
https://github.com/quarkusio/quarkus/pull/28628/files#r996786908

Additionally:

• Java 8 in JVM mode is no longer supported and the default native builder images are now Java 17 based.
• The minimum supported GraalVM version is now 22.2 so any reference to earlier versions is obsolete.
• The PR replaces links to the github repository's master branch with links to the published documentation for the corresponding GraalVM version

[gsmet]

@zakkak makes perfect sense, thanks. Would you be kind enough to rebase @galderz 's PR once this is in? I bet they are going to conflict.

[zakkak]

@zakkak makes perfect sense, thanks. Would you be kind enough to rebase @galderz 's PR once this is in? I bet they are going to conflict.

Sure, I can take care of this.

Can you think of any way to avoid running all the jobs when updating a documentation-related property in the pom files?

[gsmet]

We could move the properties to the docs pom but we need to make sure we don't forget about them.

[gsmet]

I think they were originally put there because we had other GraalVM version properties here but we moved them to Java code.

[zakkak]

We could move the properties to the docs pom but we need to make sure we don't forget about them.

Well even now the properties defining the GraalVM version are located in different properties so I think it won't make much difference:

$ rg '<graal-sdk.version'  
bom/application/pom.xml
83:        <graal-sdk.version>22.2.0</graal-sdk.version>

build-parent/pom.xml
43:        <graal-sdk.version-for-documentation>22.2</graal-sdk.version-for-documentation>

independent-projects/bootstrap/pom.xml
65:        <graal-sdk.version>22.2.0</graal-sdk.version>

I think they were originally put there because we had other GraalVM version properties here but we moved them to Java code.

OK, I am moving them in the docs pom file then.

[quarkus-bot]

Failing Jobs - Building 080dc77

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 11 Windows	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1	Build	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 18

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 Windows #

- Failing: extensions/opentelemetry/deployment 
! Skipped: integration-tests/micrometer-prometheus integration-tests/opentelemetry integration-tests/opentelemetry-grpc and 5 more

📦 extensions/opentelemetry/deployment

✖ io.quarkus.opentelemetry.deployment.instrumentation.RestClientOpenTelemetryTest.client line 65 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <SERVER> but was: <CLIENT>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

---

⚙️ JVM Tests - JDK 17 MacOS M1 #

- Failing: extensions/vertx/deployment 
! Skipped: extensions/agroal/deployment extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 341 more

📦 extensions/vertx/deployment

✖ io.quarkus.vertx.DuplicatedContextTest.testThatBlockingEventConsumersAreCalledOnDuplicatedContext - More details - Source on GitHub

(RECIPIENT_FAILURE,8185) java.util.concurrent.CompletionException: io.netty.channel.AbstractChannel$AnnotatedSocketException: Connection reset by peer: localhost/127.0.0.1:8082
	at io.vertx.core.eventbus.Message.fail(Message.java:141)
	at io.quarkus.vertx.runtime.VertxRecorder$3$1$1.handle(VertxRecorder.java:122)