Overridden Kotlin compiler version can lead to failures running detekt

[3flex]

Expected Behavior

Dependencies of detekt-cli cannot be overridden, so that specifying a specific detekt-cli version with the detekt configuration or by specifying toolVersion will always execute using a compatible Kotlin compiler version.

Observed Behavior

It's easy to override the Kotlin dependency (see #4786 (comment)) & #4813 (reply in thread), and this can happen even when users did not intend to affect the behaviour of detekt or alter its dependencies.

Steps to Reproduce

Use detekt 1.20.0, and override the kotlin compiler embeddable dependency using e.g.

configurations.matching { it.name != "detekt" }.all {
    resolutionStrategy.eachDependency {
        if (requested.group == "org.jetbrains.kotlin") {
            useVersion("1.6.10")
        }
    }
}

Context

See #4786. The actual underlying issue is that detekt-cli expects to run using a specific version of org.jetbrains.kotlin:kotlin-compiler-embeddable dependency, but the Kotlin dependency is easy to override leading to unexpected & confusing results for users.

Your Environment

• Version of detekt used:
• Version of Gradle used (if applicable):
• Gradle scan link (add --scan option when running the gradle task):
• Operating System and version:
• Link to your project (if it's a public repository):