AVRO-3852: Upgrade CI tests to Java 21 GA release

[iemejia]

What is the purpose of the change

(For example: This pull request improves file read performance by buffering data, fixing AVRO-XXXX.)

Verifying this change

(Please pick one of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Extended interop tests to verify consistent valid schema names between SDKs
• Added test that validates that Java throws an AvroRuntimeException on invalid binary data
• Manually verified the change by building the website and checking the new redirect

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[iemejia]

Ah oups it seems version 21 is not yet released ok we will have to wait a bit then.
actions/setup-java#541

[iemejia]

JDK 21 is available now so we should be good. PTAL @martin-g

[martin-g]

How does it know which version of the archetype to use ?
I expect something like -DarchetypeArtifactVersion=1.12.0-SNAPSHOT to be specified too.

[iemejia]

I did not want to do that to avoid having to update the current version on every release (usually project maintainers tend to forget that). I digged deeper and found that there is a way to do integration tests on maven archetypes so it is maybe a better solution (Avro already was doing it but it was not well configurated for modern maven standards).
https://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html

I will update this in the PR

[iemejia]

I fixed the archetypes integration tests which should pretty much cover the missing validation in each specific Java version. This should be good now. PTAL again @martin-g