Refer to the SingleJar "executable" instead of "deploy jar."

I don't think it's been a deploy jar in any environment for a while, and whatever it is, I think we run it directly as a executable.

PiperOrigin-RevId: 839725877
Change-Id: I8d8e67b3eb7bd4af11387efb727853740370f565

java/common/rules/java_toolchain.bzl

diff --git a/java/common/rules/java_toolchain.bzl b/java/common/rules/java_toolchain.bzl
index d08775a..a24ae4f 100644
--- a/java/common/rules/java_toolchain.bzl
+++ b/java/common/rules/java_toolchain.bzl
@@ -43,7 +43,7 @@
         "jvm_opt": "(depset[str]) The default options for the JVM running the java compiler and associated tools.",
         "label": "(label) The toolchain label.",
         "proguard_allowlister": "(FilesToRunProvider) The binary to validate proguard configuration.",
-        "single_jar": "(FilesToRunProvider) The SingleJar deploy jar.",
+        "single_jar": "(FilesToRunProvider) The SingleJar executable.",
         "source_version": "(str) The java source version.",
         "target_version": "(str) The java target version.",
         "tools": "(depset[File]) The compilation tools.",
@@ -546,7 +546,7 @@
             allow_files = True,
             executable = True,
             doc = """
-Label of the SingleJar deploy jar.
+Label of the SingleJar executable.
             """,
         ),
         "source_version": attr.string(