Verify server jar integrity

### Describe the problem

Hello,
I use this Docker image inside of my own mc hosting system. Sometimes when I create a new Minecraft Server, i get an corrupt jarfile Error.

"[0mError: Invalid or corrupt jarfile minecraft_server.1.19.4.jar"

Error. So I have to delete the jar-file and restart the container, which is annoying. As I built it that whay to be an autonomus system. And now I always have to look after the jar files. :/

Maybe it is possible to hash check the files? This sometimes also happens to mods in curse forge mode.

Do you really need logs and docker-compose files? The things that set them appart from the default are actually private things. The logs look normal except the Invalid or corrupt jarfile error.

Regards

### Container definition

```
Paste run command or compose file here
```

### Container logs

```
Paste logs here
```

Start by tracing the container startup path that installs or upgrades Minecraft server jars, modloaders, and modpacks. No source files or tests are named, so first locate the download and launch entry points and check how failed downloads are handled. Done means corrupt server or mod jars are detected and handled without requiring manual deletion and container restart.

Written by the indexing model from the issue text.