Add support for stripping Jar signatures when recompiling/remapping Forge

[shartte]

In "legacy" mode, we don't copy over the modding platform Jar unmodified, instead we remap and recompile the source files while copying over resources.

This breaks the Jar signatures contained in the MANIFEST.MF, so we need to do the following:

• Don't copy signature related resources (META-INF/*.{SF,RSA,EC,DSA})
• Filter out any digests from the MANIFEST.MF we copy (since the SHA-256 values will obviously differ after remapping/recompiling)
• While we're at it, don't try to copy the bogus MANIFEST.MF from the source artifact

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: c1bc942ce3e7ccab13b96bdd1cf622bdb454be4f.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged:neoform-runtime:1.0.15-pr-47-strip-jarsigning-signatures

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/NeoFormRuntime/pull/47
        url 'https://prmaven.neoforged.net/NeoFormRuntime/pr47'
        content {
            includeModule('net.neoforged', 'neoform-runtime')
        }
    }
}

[neoforged-releases]

🚀 This PR has been released as NeoFormRuntime version 1.0.12.