On MacOS, do not assume existence of Contents/Home in the JDK binary path

[GregoryTravis]

Currently when looking for the java executable on MacOS, we assume that it's under $root/Contents/Home/bin. On my M1 (running Monterey 12.6.3), using sdkman, there is no Contents/Home between $root and bin.

This change checks for the binary under Contents/Home/bin, and if it doesn't exist, defaults back to just bin.

I suspect that this depends on the OS version.

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]

Checking both locations shall not break anything.

I suspect that this depends on the OS version.

I suspect that it is the sdkman behavior.