Upgrade Java and GraalVM

[bocchino]

In CI, our GraalVM build of FPP native binaries is based on Java 11. The Java 11 version is no longer supported on the GraalVM web site:

https://www.graalvm.org/latest/docs/

It seems we should move to Java 17 or later. We should assess what is needed for this change, e.g., testing, assessing impact on users.

See update below: It looks like the Graal VM community releases, which we use, have moved on from Java 11. However, the release that we are using is still available here: https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm-22.3.3.

[LeStarch]

Several notes:

1. Java 17 is not available to us as it requires a paid license through Oracle. We will need to switch to GraalVM with Java 21 or 23
2. The critical test is if graal runs on our aarch64 hardware in CI. I will push a fix to test that.

[LeStarch]

Also: F Prime development should use the community edition: https://github.com/graalvm/graalvm-ce-builds/releases?page=1, which maintains all historical releases.

[bocchino]

It looks like Java 11 support is available there:

https://github.com/graalvm/graalvm-ce-builds/releases/tag/vm-22.3.3

This is the edition that I have on my computer (via MacPorts). @Kronos3 can you see if this distribution works for you?

[LeStarch]

Correct. I am closing this issue. We can track another issue to eventually update and reconfigure sbt in order to fix the use of a removed flag. CMSClassUnloadingEnabled.