build(distribution): re-enable SecurityManager in distributions running under Java 18 and above

[BenjaminAmos]

Contains

When running under Java 18/19, the game crashes on start-up when attempting to set a SecurityManager. SecurityManager was deprecated in Java 17 and is disabled by-default from Java 18.

This fixes #5090 by re-enabling SecurityManager in the launch scripts. The changes should only affect users running Java 18 and later.

How to test

• Build a distribution using gradlew distZip.
• Obtain a Java 19 runtime
  (I tested this with the one from https://adoptium.net)
• Temporaily set the JAVA_HOME environment variable to point at the Java 19 distribution.
• Run ./Terasology (or Terasology.bat) from the built distribution folder.
• The game should reach the main menu.

Notes

• I'm not certain that parsing the java version number in batch/sh files is going to be reliable but it seems to work. There is at least one JEP which suggests that the output format may be intentional. The parsing logic won't work with Java 8 but that's not supported for Terasology anymore, as far as I know.
• This will get you to the main menu but not much further (see Java 17 compatibility #3976 (comment) for other issues).

[Cervator]

Can confirm this tests out (on Win10 with Java 19)!

Not merging just yet although this is fine - this is the first PR I am ready to merge in what feels like ages and I want to make sure I'm up to date with the process :-)

Nicely done!