Snapshots should not be included by default

[0x189D7997]

When GitCraft is ran without any arguments it includes every single release and snapshot that has mojmaps and runs full datagen. A new user is very likely to do so without actual need, and even worse - leave the process unattended.

After running the applikation like this intentionally to test for broken versions I cannot find this behavior reasonable due to the following:

• I do see a need (other then historical) for snapshots which came out before current release (with a few exceptions like april fools), when tracking changes it is way more convenient to use full releases.
• The process took several hours on a higher end system. This has a potential to significantly waste time of a user and/or cause confusion.
• More than 30GB of client and server jars, mappings and libraries were downloaded, potentially using paid data.
• Datagen for some 1.17 snapshots has a major off-heap memory leak. With -Xmx4G this resulted in OOM killer stopping GitCraft on a system with 64GB of RAM.
• As a result more than 100GB of files were stored in the cache, this can fill up hard drive space rapidly causing all sorts of issues.
• Whole process involves a lot of disk writes (~500GB). This is a concern for SSD resource especially when using swap.

A few solutions I can suggest:

1. Set onlyStableReleases to true by default. In addition the default version range can be reduced to a few latest releases (1.20.1 and newer for example).
2. Only include snapshots released after latest stable version (and april fools ones). Combined with reduced range mentioned in 1.
3. Do not include any versions when no range or list is given. Print help and an usage example and exit.
4. When a lot of versions are included, ask a user if they really want to proceed. Possibly with a rough estimate of time, download and disk space needed.
5. If onlyStableReleases and onlySnapshots options are not specified and are not changed in the config - ask each time if snapshots should be included.