Implement support for handling Java “modules” and clean up JavaFX-specific workarounds

Created by: benfry

JavaFX 16 (which we're using as of 4.0 alpha 5) is bundled as a set of Java “modules,” rather than regular .jar files. As such, it will complain if the code is loaded from the usual CLASSPATH.

For now, there are some workarounds in the build process that treat the (newly separated) JavaFX library as a special case, but this is pretty gross, and we need to either:

1. Start tracking a modulesPath and module lists during build and bundling so that it can be specified when running from the PDE and when exporting.
2. Alternatively, we could add additional information to library.properties so that special command line options can be added. In this case, it would be --add-modules javax.base, etc, but could also be used to cover -XstartOnFirstThread for libraries that require that (LWJGL?)

首先跟踪 JavaFX 16 模块的构建和打包流程，包括 PDE 如何运行项目以及如何组装导出内容。将提议的 modulesPath/module-list 方式与通过 library.properties 添加命令行选项的方式进行比较。当 JavaFX 模块在 PDE 运行和导出过程中都无需当前的特殊处理 workaround 即可工作时，即视为完成。