Changed the publish of reobfuscated jars

[Icosider]

The problem is that MDG Legacy publishes the jar that was last reobfuscated. In the case where only shadowJar is used, this is useful, but when it is necessary to split the build into Client and Server, this functionality creates difficulties with publication.

This change allows you to specify the task that needs to be published. I also made sure that the Jar task was handled correctly.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: f6401e464ef3b7489e69e489b011905edfd7ade2.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.moddev.legacyforge:net.neoforged.moddev.legacyforge.gradle.plugin:2.0.79-pr-232-publishing-legacy
• 📦 net.neoforged.moddev:net.neoforged.moddev.gradle.plugin:2.0.79-pr-232-publishing-legacy
• 📦 net.neoforged.moddev.repositories:net.neoforged.moddev.repositories.gradle.plugin:2.0.79-pr-232-publishing-legacy
• 📦 net.neoforged:moddev-gradle:2.0.79-pr-232-publishing-legacy

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 #232' // https://github.com/neoforged/ModDevGradle/pull/232
        url 'https://prmaven.neoforged.net/ModDevGradle/pr232'
        content {
            includeModule('net.neoforged.moddev.legacyforge', 'net.neoforged.moddev.legacyforge.gradle.plugin')
            includeModule('net.neoforged.moddev', 'net.neoforged.moddev.gradle.plugin')
            includeModule('net.neoforged.moddev.repositories', 'net.neoforged.moddev.repositories.gradle.plugin')
            includeModule('net.neoforged', 'moddev-gradle')
        }
    }
}

[Icosider]

@shartte, can u toggle the checkbox?

[Technici4n]

This introduces a breaking change in the API which is quite problematic. Let's instead try to be less careless with clear() so that two subsequent reobfuscate calls work as expected.