test(gradle): Fix inert violation substring in isolated-projects assert

The old check for "problems were found reporting" never matches Gradle
output — the actual phrases are "problems were found storing the
configuration cache" or "problems were found reusing the configuration
cache". Broadening to "problems were found " catches both, so the
defensive check actually has teeth now.

Author: runningcode

plugin-build/src/test/kotlin/io/sentry/android/gradle/integration/SentryPluginIsolatedProjectsTest.kt

@@ -36,9 +36,7 @@ class SentryPluginIsolatedProjectsTest :
     // otherwise the test would silently degrade into a plain config-cache test.
     assertTrue(output) { "isolated projects" in output.lowercase() }
     assertFalse(
-      "problems were found reporting" in output ||
-        "Isolated projects violations" in output ||
-        "cannot access '" in output,
+      "problems were found " in output || "cannot access '" in output,
       "Expected no isolated-projects violations, but got:\n$output",
     )
   }