Allow disabling kotlin-metadata-jvm dependency / Kotlin metadata analysis

[robotfooder]

Plugin version
3.18.0

Gradle version
9.6.1

JDK version
21

Hi,
First of all, thank you for maintaining this plugin. We're using it across a large number of Gradle projects and have been very happy with it.
After upgrading from 3.17.0 to 3.18.0 we noticed that the plugin now creates the configuration:
dependencyAnalysisKotlinMetadataClasspath
which resolves:
org.jetbrains.kotlin:kotlin-metadata-jvm
Based on PR #1719, this appears to be used by classloader-isolated workers for Kotlin metadata processing.
Our use case is that we only analyze Java/Groovy projects and do not use Kotlin sources. Because of internal dependency governance requirements, the introduction of a Kotlin artifact in the build tool dependency graph prevents us from upgrading beyond 3.17.0.
Would it be possible to:

1. Make Kotlin metadata analysis optional, or
2. Lazily create/resolve dependencyAnalysisKotlinMetadataClasspath only when Kotlin support is actually needed, or
3. Provide a feature flag to disable Kotlin metadata processing entirely?

We would be happy to continue upgrading the plugin if there were a way to avoid resolving org.jetbrains.kotlin:kotlin-metadata-jvm for non-Kotlin projects.
Thanks!

[autonomousapps]

the introduction of a Kotlin artifact in the build tool dependency graph

This is inaccurate. This plugin has used the kotlin-metadata-jvm artifact for years. The change in 3.18.0 is that it's been moved to a new configuration so that it's now only used in classloader-isolated workers, rather than on the primary build classpath.

[robotfooder]

Sorry for the wrong statement, but the introduction of the new configuration triggers our OSS check and we cant use the 3.18.0 version. Is it possible to opt-out of the new configuration?

[autonomousapps]

Your OSS check is wrong. If you check 3.17.0 you will see that dependency was present. Simply inspecting any of the POMs going back years will demonstrate this fact.

You're welcome to contribute a PR, and if I think the maintenance burden won't be too high (which I can't guarantee), I may accept it. If contributing interests you, please see the code of conduct and contributing guides.

Alternatively, I am available for hire if you would like to sponsor me to contribute this on your behalf. Feel free to email me.