AUTO_CURSEFORGE - Error after backup restores

A clean setup works great. If the application is removed and added back fresh but there is a backup that can be restored, it will fail every time in the main pod/container.
This creates a crashloopback and the server never starts up.
My guess is the restore of the backup is lacking some data that it doesn't know what to do. I think it might be fixed if we could force a reinstall of the forge mod loader every time it boots up. Takes longer to boot but its worth it.
Could also tackle the issue of the possible missing files that don't get backed up. I turned off any exclusions by the way. So it should be getting everything from /data and it looks like it does when I compare the data.

```
[mc-image-helper] 21:28:51.153 INFO : Forge version 47.3.0 for minecraft version 1.20.1 is already installed
[init] Setting mode
[mc-image-helper] 21:28:52.982 INFO : Created/updated 1 property in /data/server.properties
[init] Setting initial memory to 12G and max to 12G
[init] Using Forge supplied run.sh script...
WARNING: Unknown module: cpw.mods.securejarhandler specified to --add-exports
WARNING: Unknown module: cpw.mods.securejarhandler specified to --add-opens
WARNING: Unknown module: cpw.mods.securejarhandler specified to --add-opens
Error: Could not find or load main class cpw.mods.bootstraplauncher.BootstrapLauncher
Caused by: java.lang.ClassNotFoundException: cpw.mods.bootstraplauncher.BootstrapLauncher
2025-02-18T21:28:53.154Z WARN mc-server-runner Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error. {"exitCode": 1}
2025-02-18T21:28:53.154Z INFO mc-server-runner Done
```

The issue names no repository files or tests. Start by reproducing a backup restore in the Docker container and inspect the Forge startup output, especially the missing BootstrapLauncher class. Done means a restored server completes startup instead of entering a crash loop.

Written by the indexing model from the issue text.