JUnit is leaked on debug classpath

[Ilia Voitcekhovskii]

Describe the bug
I had issues with running LeakCanary on our build because it detects JUnit on our debug classpath.
We setup all test dependencies properly - so we check where junit is coming from.

As you can see, one of dependencies of Wallet Connect is using junit and leaking it in classpath: com.github.komputing.kethereum

SDK Version

• Client: Kotlin
• Version 1.31.4

As a workaround for now i just remove junit from WC dependency:

    implementation(platform(libs.walletconnect.bom))
    implementation(libs.walletconnect.android) {
        exclude(group = "org.bouncycastle", module = "bcprov-jdk15on")
        exclude(group = "junit", module = "junit")
    }
    implementation(libs.walletconnect.sign) {
        exclude(group = "org.bouncycastle", module = "bcprov-jdk15on")
        exclude(group = "junit", module = "junit")
    }