同时检查 JarPath 是否包含 !

[CiiLu]

突然发现不光运行路径，Jar路径也不能包括 !，否则也会报错

Exception in thread "main" java.lang.NullPointerException
        at java.base/java.io.Reader.<init>(Reader.java:286)
        at java.base/java.io.InputStreamReader.<init>(InputStreamReader.java:119)
        at org.jackhuang.hmcl.util.SelfDependencyPatcher$DependencyDescriptor.readDependencies(SelfDependencyPatcher.java:108)
        at org.jackhuang.hmcl.util.SelfDependencyPatcher.<init>(SelfDependencyPatcher.java:76)
        at org.jackhuang.hmcl.util.SelfDependencyPatcher.patch(SelfDependencyPatcher.java:176)
        at org.jackhuang.hmcl.EntryPoint.checkJavaFX(EntryPoint.java:207)
        at org.jackhuang.hmcl.EntryPoint.main(EntryPoint.java:58)
        at org.jackhuang.hmcl.Main.main(Main.java:107)

之前运行路径的检查也需要保留，否则 JavaFX 可能会无法加载 css 样式

[Glavo]

请检查 CodeSource 是否为 null。

[Copilot]

Pull request overview

Adds an additional startup validation to prevent launching HMCL from locations that contain !, extending the existing working-directory check to also cover the HMCL jar path to avoid downstream runtime errors.

Changes:

• Read the HMCL jar path from Main.class CodeSource and check whether it contains !.
• Show an error dialog and exit when the jar path contains ! (in addition to the existing working-directory check).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Main.class.getProtectionDomain().getCodeSource().getLocation() can be null in some classloading scenarios; calling .getPath() unconditionally introduces a new potential NPE during startup. Consider retrieving the CodeSource/Location with null + SecurityException handling (and only computing the jar path after the working-dir check) so checkDirectoryPath() never crashes before showing an error dialog.

[Copilot]

In the jar-path ! branch, the dialog prints currentDir instead of thisJarPath, which will mislead users about which path is invalid. Use the jar path variable (and consider aligning the wording with the stderr message).

Suggested change

	SwingUtils.showErrorDialog("Exclamation mark(!) is not allowed in the path where HMCL is in.\n" + "The path is " + currentDir);
	SwingUtils.showErrorDialog("Exclamation mark(!) is not allowed in the jar path.\n" + "The path is " + thisJarPath);

[Copilot]

The new jar-path validation is startup-critical but currently hard to test because checkDirectoryPath() is private and exits the JVM/UI-calls directly. Consider extracting the core validation into a package-private pure method (e.g., taking currentDir and jarPath and returning an optional error) and add unit tests for both working-dir and jar-path cases.