Fix published dependencies

[lukebemish]

There are two current issues with the jst-cli-bundle publication that result in wacky metadata. First, the shadow.component(...) method is used to add the shadow jar to the publication -- this approach does not, in fact, use a component, but just manually adds the artifact, and adds dependencies to the pom. This probably helped hide the actual issue a bit -- the actual issue being that shadowRuntimeElements.extendsFrom shadow within the shadow plugin itself, as the shadow plugin uses the shadow configuration to mean "things you're not bundling, and hence need to publish a dependency on". However, the jst-cli buildscript reuses this name for "things that should be bundled" and so the jst-cli-bundle published a dependency on everything it bundled. This PR fixes this, and uses a component for publishing so we get gradle module metadata.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 6e14bb4041ec32c3147b22f2616c45906fcf8830.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.jst:jst-cli:1.0.66-pr-37-fix-publishing
• 📦 net.neoforged.jst:jst-cli-bundle:1.0.66-pr-37-fix-publishing
• 📦 net.neoforged.jst:jst-api:1.0.66-pr-37-fix-publishing

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 #37' // https://github.com/neoforged/JavaSourceTransformer/pull/37
        url 'https://prmaven.neoforged.net/JavaSourceTransformer/pr37'
        content {
            includeModule('net.neoforged.jst', 'jst-cli')
            includeModule('net.neoforged.jst', 'jst-cli-bundle')
            includeModule('net.neoforged.jst', 'jst-api')
        }
    }
}

[neoforged-releases]

🚀 This PR has been released as JavaSourceTransformer version 1.0.64.