[FG7] Add a way to configure Tools (Mavenizer/Slimelauncher)

[RealMangorage]

This is mainly a PR to discuss the most ideal way of handling the configurability of these tools that FG7 uses.

The build script would look like this, to override a tool.

dependencies {
    mavenizer "net.minecraftforge:minecraft-mavenizer:0.3.3"
    slimelauncher "net.minecraftforge:slime-launcher:0.1.0"

    implementation(minecraft.dep("net.minecraftforge:forge:1.21.5-55.0.23"))
}

[Jonathing]

There are a couple of things about your implementation I don't like. But with regards to what we want to add, I do like this.

Originally, I was planning something like this:

minecraft {
    mavenizer = 'me.jonathing:mavenizer:0.3.0'
}

But this works better. I do think I need to clean up a bit of my code with the Tools enum, it's not entirely finished.

[RealMangorage]

I did it this way, as to not change any method signatures, just add new ones, as I was not entirely sure how you wanted to deal with it.

I can go thru everything (my impl) and clean it up for you, if you would like to.

[Jonathing]

I think this whole bit might be better in an extension. I'm still thinking of potentially an alternate implementation? One that looks like this:

dependencies {
    fgTools.mavenizer 'me.jonathing:mavenizer:0.3.0'
}

To do that, I'd need to make a new extension for DependencyHandler that returns configurations. If you'd like to present your own take on this, feel free.

[Jonathing]

For the record, this absolutely can be transitive. Instead of having Tools return a Provider<File>, it would instead be better to use the configuration you created in ForgeGradlePlugin, add the default tool to that configuration, and then use that as the classpath in the task.

[RealMangorage]

Ah great! I will fix that.