Forge Server Unable to derive server jar for Forge for Version 1.18.*

### Describe the problem

Hello, since I tried to update to some newer Versions e.g 1.17* I am getting those errors in the logs. It seems like something is wrong, but I cant figure out what is wrong. I can literally type VERSION: 1.15.2 start docker compose and its working, but when I write 1.18.2 in the Version field it does not work. I tried my old config and just the basic one from here. I can also give you the whole log, but I would prefere to do this via file since there are like 18k lines.

### Container definition

```
version: "3.8"

services:
mc:
image: itzg/minecraft-server
ports:
# expose the Minecraft server port outside of container
- "25565:25565"
environment:
# REQUIRED for all types
EULA: "TRUE"
# Set server type (vs the default of vanilla)
TYPE: FORGE
DEBUG: "true"
VERSION: 1.18.2
volumes:
# use a named, managed volume for data volume
- /home/nicolas/minecraft-server-docker/server/data:/data
# attach local host directory "mods" in same directory as this compose file
# all mods in this directory get copied into /data/mods at startup
- /home/nicolas/minecraft-server-docker/server/data/mods:/mods:ro

volumes:
# declared the named volume, but use default/local storage engine
mc_forge: {}
```
The compose.yaml is basically the one from github. Slightly adjusted at path and version.

### Container logs

```
mc_1 | [init] Finding installed server jar...
mc_1 | [init] Unable to derive server jar for Forge
```

No source file or test is named. Reproduce the failure with TYPE=FORGE, VERSION=1.18.2, and DEBUG=true using the supplied compose configuration, then trace the startup path that reports “Unable to derive server jar for Forge.” Done means the same configuration starts successfully and the server jar is found.

Written by the indexing model from the issue text.