Different Launcher / Chunky JVM issues

Odd issue that crops up from time to time for some reason.

It is possible to launch Chunky Launcher, via commandline (`java -jar chunkylauncher.jar`) or double clicking, and get a `Cannot find JavaFX` error while the Java Runtime is set to JVM 8. ie - `Java` is set to JVM 17 which can cause the `Cannot find JavaFX` error to occur. However you will then be met with a `Launch Error` after fixing JFX as the actual Java Runtime set within the Launcher is JVM 8.

This typically occurs if someone has previously used/attempted to use Chunky with JVM 8 and then proceeds to try JVM 17. The act of installing JVM 17 would update the default JVM and thus lead to this issue occurring.

---

While I understand that having a different JVM for the Launcher and Chunky may have uses...

- Do not auto populate `Java Options` with `--module-path` and `--add-modules` if the `Java Runtime` is set to JVM 8 even if the Launcher detects JVM 17 being used and finds JFX.
- If a different JVM to what the Launcher is using is found in the `Java Runtime` field, query the user: `Ignore`, `Let me pick (and ignore)`, `Use Launcher JVM (and auto populate Java Options)`.

Start by reproducing the launcher from the command line and by double-clicking with JVM 8 and JVM 17, then inspect how Java Runtime and Java Options are detected and populated. Done means JVM 8 does not receive JavaFX module options and a mismatch prompts the user with the three requested choices.

Written by the indexing model from the issue text.