Fix GraalVM distribution download on MacOS

[Akirathan]

Pull Request Description

Follow-up of recent GraalVM update #7176 that fixes downloading of GraalVM for Mac - instead of "darwin", the releases are now named "macos"

Important Notes

Also re-enables the JDK/GraalVM version check as onLoad hook to the sbt process. We used to have that check a long time ago. Provides errors like this one if the sbt is run with a different JVM version:

[error] GraalVM version mismatch - you are running Oracle GraalVM 20.0.1+9.1 but GraalVM 17.0.7 is expected.
[error] GraalVM version check failed.

Checklist

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

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[JaroslavTulach]

I am surprised we haven't seen some failures before this fix.

[Akirathan]

I am surprised we haven't seen some failures before this fix.

I should have asked for QA on MacOS. I have only asked for QA on Windows. That is why I have not spotted this error. Until this is solved, I believe that also nightly builds for MacOS will be failing.

[mwu-tow]

This breaks build in another place, see the run results:

/Users/runner/work/enso/enso/built-distribution/enso-engine-2023.2.1-dev-macos-amd64/enso-2023.2.1-dev/bin/enso: No such file or directory

[Akirathan]

This breaks build in another place, see the run results:

/Users/runner/work/enso/enso/built-distribution/enso-engine-2023.2.1-dev-macos-amd64/enso-2023.2.1-dev/bin/enso: No such file or directory

I think I have just discovered the problems with the IDE building. It seems that I have accidentally broken ./run backend build and ./run ide build, both for Linux and Mac. How is it possible that it passed all the tests? Do we not do ./run ide build on the CI tests?