Add various CLI options for custom Launcher use-cases

[shartte]

Introduces the following CLI options:

Option	Description
--libraries <folder>	Overrides the directory where libraries will be downloaded to, and generated files such as the patched Minecraft jar will be stored.
--versions <versions>	Overrides the directory where the installer looks for Vanilla client jars and stores them if it has to download them.
--no-minecraft-launcher-profile	Skips adding a profile to the Vanilla launcher, this also disables the check whether the target directory for a client installation is a valid Vanilla launcher directory.
--write-merged-version-json <path>	If given, the installer creates a Vanilla Launcher version json for the NeoForge version that is being installed. This JSON file will have no inheritFrom fields, and will fully describe how to launch the game.
--no-download-libraries	Disables downloading of any libraries beyond the libraries needed to perform the installation.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 306493cb9f29e7698a40c7f526570fa4979a21ff - version: 3.0.47-pr-47-launcher-options

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged:legacyinstaller:3.0.47-pr-47-launcher-options

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name = "Maven for PR #47" // https://github.com/neoforged/LegacyInstaller/pull/47
        url = uri("https://prmaven.neoforged.net/LegacyInstaller/pr47")
        content {
            includeModule("net.neoforged", "legacyinstaller")
        }
    }
}