How to use `remote_java_repository` with a JDK release where Java home is nested?

I'm trying to use `remote_java_repository` with GraalVM releases on MacOS.

When extracting the package the layout is of the form:
```
└── Contents
├── Home
│   ├── bin
│   │   ├── java
│   │   ├── javac
```

There are no top level symlinks into the nested `bin` directory as can be seen in the Zulu JDK releases that `remote_java_repository` is normally used with.

Would it be possible to make this rule configurable so that the path to the Java home inside the extracted distribution can be customized?

Start at the remote_java_repository rule and reproduce the GraalVM MacOS archive layout shown in the issue, including Contents/Home/bin. Determine how the extracted Java home is currently located; done means the rule can select that nested path and successfully use the JDK without top-level symlinks.

Written by the indexing model from the issue text.