fix(graalvm): update to Oracle Linux 10 to fix file command mimetype issues

[AlexTMjugador]

While PR #3763 ensured that the Minecraft container no longer starts too early relative to the Nginx container during test execution, it didn't actually resolve the execution errors that appeared after upgrading the GraalVM images to Oracle Linux 9.

Luckily, after clearing my local Docker build cache, I was finally able to reproduce the issue locally using the commands outlined at #3762 (comment). This allowed me to investigate the problem more deeply.

Using docker exec, I traced the root cause to a broken file command in Oracle Linux 9, which inconsistently reports MIME types for ZIP files. Some ZIP files I tested with were correctly identified as application/zip, but the problematic file, tests/setuponlytests/generic-packs/web/configs.zip, was an exception, as shown in https://github.com/itzg/docker-minecraft-server/actions/runs/19390730903/job/55483795809. Interestingly, the file command correctly identifies it as a ZIP file when the --mime-type flag is omitted: the issue lies solely in the MIME-type output.

Consequently, I decided to upgrade the base image to Oracle Linux 10, released in June 2025, ensuring the OS environment is as up-to-date as it gets. (For context, Oracle Linux 8, used before the bump to OL9, was originally released in 2019.) This update resolved the ZIP MIME-type inconsistencies, requiring only minor adjustments to the install-packages.sh script to account for naming changes in the latest OS release.

I've verified these changes to successfully restore passing CI results for GraalVM by achieving successful GraalVM workflow runs, which can be seen here. (Only Alpine images are failing, but that's unrelated to any of the PRs I submitted lately.)

Thanks again to @itzg for the helpful pointers at #3763 (comment) and the prompt reviews!

[itzg]

Awesome! Great research and glad to hear it was reproducible for you. Good call on going to the very newest in any case.