Fix old server version parsing

[js6pak]

Strips the starting message from the version string

Examples of strings in old server versions

1.0.0 - Starting minecraft server version 1.0.0

b1.7.3 - Starting minecraft server version Beta 1.7.3
b1.0 - Starting minecraft server version Beta 1.0

a0.2.8 - Starting minecraft server version 0.2.8
a0.1.0 - Starting minecraft server version 0.1.0

Afaik there is no way to extract the version from classic server jars

Problem with alpha

Alpha server versions are independent from client versions and have a leading zero which the version regex doesn't support

[sfPlayer1]

If it isn't possible to infer the correct version id as used by launchermeta from these strings directly, it may be appropriate to have a hardcoded translation table (Map) for all weird cases.

Please add some more comments around which versions use the various code paths and why, including examples (something like // used by MC beta 1.0-1.7.3 dedicated server: Starting minecraft server version Beta 1.7.3)

[js6pak]

All versions before 1.2.5 don't have the server included in launchermeta. Only way to get those is betacraft's server archive and omniarchive index

And it's not really possible to translate alpha server versions to clients because there were multiple server releases with the same protocol version and no client counterpart, and vice versa
So I guess the only way to go about it is to treat server & client independently and allow leading zero in alpha version regex