Explain Kotlin warning mode compatibility patch

Document why javac warning propagation must stay separate: on JDK 25 the Java 8 target's obsolete options warnings otherwise become fatal under Kotlin warn=error.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jketema

misc/bazel/registry/modules/rules_kotlin/2.4.21-codeql.1/patches/codeql_do_not_propagate_kotlin_warning_mode_to_javac.patch

@@ -1,5 +1,7 @@
-Keep Kotlin warning settings scoped to Kotlin compilation. In particular, do not
-turn javac warnings into errors when Kotlin's warn = "error".
+rules_kotlin 2.4 propagates the Kotlin warning mode to javac, so the extractor's
+Kotlin warn = "error" setting also makes Java warnings fatal. This breaks the
+Java 8 target with JDK 25's obsolete source/target option warnings. Keep Kotlin
+warnings-as-errors for Kotlin compilation without changing javac warning behavior.
 --- a/kotlin/internal/jvm/compile.bzl
 +++ b/kotlin/internal/jvm/compile.bzl
 @@ -1162,21 +1162,6 @@

misc/bazel/registry/modules/rules_kotlin/2.4.21-codeql.1/source.json

@@ -4,7 +4,7 @@
     "patches": {
         "codeql_add_language_version_option.patch": "sha256-ml0fzhPwNozMi6yKtEn9YLM8LSQE4BWiimdwYzennCo=",
         "codeql_do_not_emit_jdeps.patch": "sha256-yoBFnSWJyeF+gyhX+03TMTnRxUQJjup/f/KORdxVsAE=",
-        "codeql_do_not_propagate_kotlin_warning_mode_to_javac.patch": "sha256-IWR4wEbHNEcaAAwFnZA2uHy99kviyuLr5mjzc1TOTMs="
+        "codeql_do_not_propagate_kotlin_warning_mode_to_javac.patch": "sha256-TvfKfINvi1/tcLq3HDUs2doD4kr8AkMv0nsZvUHPjwg="
     },
     "patch_strip": 1
 }