MacOS deployment fails when main class is in a different package

Good morning!

I've found the following issue

**Given** the `Hello world!` project
**And** the `main.kt` file is moved to a different package `com.demo`
**And** the `korge.jvmMainClassName` is set to `com.demo.MainKt`
**And** run the MacOS deployment command as follows `./gradlew clean packageJvmMacosApp`
**When** running the `build/platforms/jvm-macos/game` app
**Then**
- **Expected**: it runs correctly the `Hello World!` game
- **Actual**: it try to opens but crashes

**Additional information**
When running the generated jar file with the command `java -jar build/libs/korge-hello-world-all.jar` it works correctly.

Based on that, my assumption is that the problem is only related to the MacOS deployment in this case.

Reproduce the issue in the Hello world project by moving main.kt to com.demo, setting korge.jvmMainClassName to com.demo.MainKt, and running ./gradlew clean packageJvmMacosApp. Compare the generated build/platforms/jvm-macos/game app with the working build/libs/korge-hello-world-all.jar. Done means the packaged macOS app launches and runs the game when the main class is in another package.

Written by the indexing model from the issue text.