MRI-3601 Bazel: generation output is not invalidated on generator change

GitOrigin-RevId: eaec51070f5d5c0367daa535a0eefc7ea855b38b

MODULE.bazel.lock

@@ -339,7 +339,7 @@
     },
     "//build:jps_dynamic_deps_community.bzl%jps_dynamic_deps_community_extension": {
       "general": {
-        "bzlTransitiveDigest": "dIJG254CjU7bCezGzKaPiIom96AuSeLKVqlLlDedQY4=",
+        "bzlTransitiveDigest": "7cd17hVeUPGUkB4O937iEweB6G8hAl2j6fbUjCM7yCU=",
         "usagesDigest": "OSsQY2hkpxdAkgfVzTh+Q1KLtzAuQDVI0/8sRki7FfU=",
         "recordedFileInputs": {},
         "recordedDirentsInputs": {},

build/jps_dynamic_deps_community.bzl

@@ -71,6 +71,9 @@ def _targets_repo_impl(ctx):
             .get_child("jpsModelToBazelCommunityOnly.cmd")
     )
 
+    # Invalidate results when generator or its settings change
+    ctx.watch_tree(root.get_child("platform").get_child("build-scripts").get_child("bazel"))
+
     # jps-to-bazel.cmd internally runs `bazel run` to execute the converter.
     # This "bazel inside bazel" works because repository rules execute during the loading phase,
     # before the current build's analysis phase starts. The inner bazel invocation is a completely