[pavog]

[16:42:07 ERROR]: [Configurations] Loading a newer configuration than is supported (999 > 31)! You may have to backup & delete your global config file to start the server.
[16:42:07 ERROR]: [Configurations] Loading a newer configuration than is supported (999 > 31)! You may have to backup & delete the world defaults config file to start the server.
[16:42:07 ERROR]: [Configurations] Loading a newer configuration than is supported (999 > 31)! You may have to backup & delete the minecraft:the_nether config file to start the server.

Paper logs this when a config file has a higher _version than the server supports, usually after a downgrade.
Nothing was detected before.
This PR adds a problem that names the affected config and both config versions.
It suggests backing up and deleting the file, or installing the newer Paper version again.

The global and world defaults configs are reported with their path.
A single world's config is reported by world name only.
Its location depends on the Paper version: up to 1.21 it was world_nether/paper-world.yml, but since 26.1 it is world/dimensions/minecraft/the_nether/paper-world.yml, while the log still says world_nether.
Newer builds name the world by its key (minecraft:the_nether), so both forms are matched.

The reset solution is deliberately not automatable, because deleting the file loses all settings in it.
VersionDowngradeSolution is not reused, because config versions also change between Paper builds of the same Minecraft version.

A custom config folder (--paper-settings-directory) is not covered: the paths always assume config/.

Changes

• add NewerConfigVersionProblem to the Paper analyser
• add PaperConfigResetSolution, PaperWorldConfigResetSolution and PaperInstallNewerVersionSolution
• add translations for the problem and the solutions
• add paper-newer-config-version-26-3.log (global, world defaults, world key)
• add paper-newer-world-config-version-26-1-1.log (world defaults, world name)