Add some engine jobs that run with Oracle GraalVM

[Akirathan]

Closes #9266.

Pull Request Description

Adds Oracle GraalVM configuration for some backend jobs. Oracle GraalVM jobs run only on Linux so far. The old jobs use GraalVM CE.

Important Notes

• The JDK to download and use is deduced from the JAVA_VENDOR environment variable. By default, GraalVM CE is used.
• sbt can be started with both GraalVM CE and Oracle GraalVM without any warnings.
  • If you try to start sbt with JDK from a different vendor, but with the same Java version, a warning is printed.

Current list of jobs in the Engine CI workflow (these jobs are visible on this PR, because they are scheduled to run on every PR):

• Engine (GraalVM CE) (linux, x86_64)
• Engine (GraalVM CE) (macos, x86_64)
• Engine (GraalVM CE) (windows, x86_64)
• Engine (Oracle GraalVM) (linux, x86_64)
• Scala Tests (GraalVM CE) (linux, x86_64)
• Scala Tests (GraalVM CE) (macos, x86_64)
• Scala Tests (GraalVM CE) (windows, x86_64)
• Scala Tests (Oracle GraalVM) (linux, x86_64)
• Standard Library Tests (GraalVM CE) (linux, x86_64)
• Standard Library Tests (GraalVM CE) (macos, x86_64)
• Standard Library Tests (GraalVM CE) (windows, x86_64)
• Standard Library Tests (Oracle GraalVM) (linux x86_64)
• Verify License Packages (linux, x86_64)

Benchmark Engine workflow (not visible on this PR, cannot schedule manually yet):

• Benchmark Engine (GraalVM CE)
• Benchmark Engine (Oracle GraalVM)

Benchmark Standard Libraries workflow (not visible on this PR, cannot schedule manually yet):

• Benchmark Standard Libraries (GraalVM CE)
• Benchmark Standard Libraries (Oracle GraalVM)

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• Ensure Oracle GraalVM is downloaded and used in the new jobs.

[JaroslavTulach]

Oracle GraalVM seems to be downloaded and seems green. The same applies for scala tests on Oracle GraalVM.

But where are GraalVM CE tests on Linux? Shouldn't we run both?

[mwu-tow]

I am impressed with how well you deal with the build script! 👍

I have a bunch of comments, mostly stylistic.

[JaroslavTulach]

I am concerned by changes and renames to existing CI actions. I'd prefer to leave them as unchanged as possible. I am afraid the rename will affect other tools that rely on the existing name. Otherwise looks fine.