Exclude ktlint configurations from strict version conflict checking

The `ktlint` plugin (v14.1.0) introduces internal version conflicts between
transitive dependencies (e.g., `sarif4k` 0.5.0 vs 0.6.0 and `kotlin-logging`
5.1.0 vs 7.0.3) when resolving its reporter and tool configurations.

Since these conflicts are internal to the linting tool and do not affect
the project's production runtime, this change bypasses the global
`failOnVersionConflict()` strategy for any configuration starting with 'ktlint'.
This allows Gradle's default conflict resolution to pick a functional version
and fixes the `loadKtlintReporters` task failure.

Signed-off-by: Junie <junie@jetbrains.com>

Author: gesellix

build.gradle.kts

@@ -32,13 +32,15 @@ val dependencyGroupVersions = mapOf<String, String>(
 
 subprojects {
     configurations.all {
-        resolutionStrategy {
-            failOnVersionConflict()
-            force(dependencyVersions)
-            eachDependency {
-                val forcedVersion = dependencyGroupVersions[requested.group]
-                if (forcedVersion != null) {
-                    useVersion(forcedVersion)
+        if (!name.startsWith("ktlint")) {
+            resolutionStrategy {
+                failOnVersionConflict()
+                force(dependencyVersions)
+                eachDependency {
+                    val forcedVersion = dependencyGroupVersions[requested.group]
+                    if (forcedVersion != null) {
+                        useVersion(forcedVersion)
+                    }
                 }
             }
         }