294bd8c7fa
When Gradle resolves a dependency on a publication with no metadata (or with metadata disabled), it represents it as two variants, one with Usage `java-api`, the other with `java-runtime`. It turns out that the `java-api` one does not contain transitive dependencies with Maven scope `runtime`. This commit makes the Kotlin Gradle plugin disambiguation rules behave the same way as those defined in the JavaBasePlugin: when no Usage is requested, prefer the runtime usages as they are more complete.