Use bootclasspath jar in proguard genrule

Previously, proguard may attempt to access the Java runtime jmods, which aren't declared as inputs.

Fixes bazelbuild#22787 (comment)

Closes bazelbuild#23067.

PiperOrigin-RevId: 655470599
Change-Id: I5ff6cd9c32f553fc3d8364ba1b6a4f4e3417418b

third_party/BUILD

@@ -309,13 +309,14 @@ genrule(
     name = "fastutil_stripped_jar",
     srcs = [
         "@maven//:it_unimi_dsi_fastutil_file",
+        "@rules_java//toolchains:platformclasspath",
     ],
     outs = ["fastutil-stripped.jar"],
     cmd = """
     $(location :proguard) \
-        -injars $< \
+        -injars $(execpath @maven//:it_unimi_dsi_fastutil_file) \
         -outjars $@ \
-        -libraryjars '<java.home>/jmods/java.base.jmod(!**.jar;!module-info.class)' \
+        -libraryjars $(execpath @rules_java//toolchains:platformclasspath) \
         @$(location //tools:fastutil.proguard) \
       | tail -n +2 # Skip the "ProGuard, version X" line
     # Null out the file times stored in the jar to make the output reproducible.