Update target platform to work with Big Sur

[thSoft]

On macOS 11 Big Sur, starting the Elysium launch configuration fails with:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=54117, tid=775
#
# JRE version: OpenJDK Runtime Environment (11.0.2+9) (build 11.0.2+9)
# Java VM: OpenJDK 64-Bit Server VM (11.0.2+9, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# C  0x0000000000000000
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/thsoft/Development/elysium/Eclipse.app/Contents/MacOS/hs_err_pid54117.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

The launch configuration command line is:

/Users/thsoft/.sdkman/candidates/java/11.0.2-open/bin/java
-XstartOnFirstThread
-Xmx1024m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.internal.carbon.smallFonts
-Dorg.osgi.framework.bundle.parent=ext
-Declipse.pde.launch=true
--add-modules=ALL-SYSTEM
-Dfile.encoding=UTF-8
-classpath /Users/thsoft/.p2/pool/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar org.eclipse.equinox.launcher.Main
-launcher /Users/thsoft/Development/elysium/ws/.metadata/.plugins/org.eclipse.pde.core/.install_folders/1609691687860/Eclipse.app/Contents/MacOS/eclipse
-name Eclipse
-showsplash 600
-product org.eclipse.platform.ide
-data /Users/thsoft/Development/elysium/ws/.runtime/Elysium
-configuration file:/Users/thsoft/Development/elysium/ws/.metadata/.plugins/org.eclipse.pde.core/Elysium/
-dev file:/Users/thsoft/Development/elysium/ws/.metadata/.plugins/org.eclipse.pde.core/Elysium/dev.properties
-os macosx
-ws cocoa
-arch x86_64
-nl hu_HU
-consoleLog

/Users/thsoft/.p2/pool/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar is of a suspiciously old version, so updating the target platform might solve the problem.