[7.0] Intentionally support the Configuration Cache

[Jonathing]

The Configuration Cache is an optimization feature in Gradle which makes it attempt to skip the configuration phase of a Gradle invocation in order to save build time when running tasks repeatedly.

Support for this is highest priority, as the configuration cache has proven to save time in builds across a variety of projects, and will also be the default execution mode in Gradle 10.

So far, ForgeGradle 7 supports the configuration cache as all plugins, extensions, and tasks have been created with it in mind, using the proper properties and (Gradle-managed) types. However, I'm creating this issue to ensure that I don't break configuration caching by accident for any updates I make to ForgeGradle 7 until stabilization.

This issue will be closed as complete once ForgeGradle 7 is stabilized.

cc @PaintNinja @mezz

[Jonathing]

Unfortunately hit a bit of a regression on this. Here's the relevant yappage on Discord in case it interests you:
https://discord.com/channels/1129059589325852724/1129095235889270844/1427830987672260730

In short, I just need to re-implement the Mavenizer invocation again to be a task. Need to make it in a way where it always runs if there's some sort of change to the Minecraft dependency.

[Jonathing]

Configuration cache compatibility has been restored by #996.