Embedded Kotlin dependencies should resolve with correct metadata

[eskatos]

This issue is a follow up to #10697 for which a quick fix #10691 was made for 5.6.3. This issue is about reworking the way dependencies to the embedded Kotlin version are declared in order to prevent issues like #10697 to happen again.

Expected Behavior

Gradle should resolve embedded kotlin dependencies with correct metadata.

Gradle should provide explaining reasons when facing a conflicts with the embedded kotlin version in build scripts classpath.

Current Behavior

The dependency graph of embedded Kotlin dependencies is hardcoded in the Kotlin DSL codebase, making use of a graph of ClientModules instead of proper resolved metadata. This makes it fragile as it needs to be updated each time we upgrade the embedded Kotlin version to reflect a possibly new dependency graph.

Moreover the pinning of those dependencies in the buildscript classpath is done using a dependency resolution rules, which can't provide any explanation to users when facing a conflict.

Context

#10697

[eskatos]

Fixed in #10701