1.9 release causes incorrect forge file to be called

[danpolanco]

forge-1.9-11.15.1.1722-universal.jar should be forge-1.8.9-11.15.1.1722-universal.jar. For prosperity, @itzg created a ComparableVersions for that reason and it just needs to be altered to fix this.

I believe the shell script just needs to be updated.

[summarized from Slack chat]

[danpolanco]

Ok. I figured it out. My docker compose file was creating the container without setting the VERSION environment variable. That meant it was assuming 1.8.9, however, 1.9 came out, it assumed 1.9 was the primary version which didn't match the forge version I selected.