Document missing resource transformers

[Goooler]

No description provided.

[Copilot]

Pull request overview

This PR updates Shadow’s documentation to better cover “missing” resource transformers and modernize Gradle DSL examples (Kotlin/Groovy) for configuring resource merging and transformations.

Changes:

• Modernizes transform(...) usage examples (Kotlin trailing-lambda style, Groovy configuration avoidance via tasks.named).
• Expands documentation for additional transformers (e.g., Properties merging, Apache NOTICE, Plexus components XML, deduplication/preserve-first semantics).
• Adds/updates API reference links for newly documented transformers and constants.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
docs/kotlin-plugins/README.md	Updates Kotlin/Groovy examples for Kotlin module metadata transformer configuration.
docs/configuration/merging/README.md	Modernizes transform examples and adds/expands sections documenting additional built-in resource transformers and configuration patterns.

Suppressed comments (2)

docs/configuration/merging/README.md:555

• In Kotlin DSL, resource is a Gradle Property<String> on XmlAppendingTransformer; configure it via .set(...) instead of =.

      transform<com.github.jengelman.gradle.plugins.shadow.transformers.XmlAppendingTransformer> {
        resource = "properties.xml"
      }

docs/configuration/merging/README.md:752

• In Kotlin DSL, these transformer fields are Gradle Property<String> values; assigning with = won’t compile. Use .set(...) for each property.

        projectName = "My Project"
        organizationName = "My Organization"
        organizationURL = "https://example.com"
        inceptionYear = "2024"

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.