Show a range of supported versions instead of just 1.X

[misode]

No description provided.

[Bloo-dev]

Currently output.py specifies supported Minecraft versions for pushing releases to Modrinth and Smithed. These Minecraft Versions are fixed per major release version and do currently not reflect the actual minor versions supported by our data packs.

This is a major issue, not only for the website (which will only show supported major Minecraft versions), but also for Modrinth and Smithed, where data packs will be released and listed by minor versions, however, these do not reflect the intended version coverage by the data pack developer.

The following solution has been proposed in a related conversation on discord (private channel, hence no link):

[Bloo:] In output.py we'll continue to specify supported versions as a fallback, however, each module can also specify its own supported versions in its beet.yaml which must be subset of the supported versions in output.py. If a module does not specify its own set, the set from output.py is used.

We should use data pack versions for all version specifications mentioned above and only translate those to minecraft versions when the modules are published to vendors (gm4.co, Morinth, Smithed).

Furthermore, some of our data packs currently specify a set of data pack versions with their overlays. These data pack versions must be subset of the supported versions listed in the packs beet.yaml:

[Misode:] [...] all the overlay ranges need to fit in the supported versions field (which could be validated by a plugin)