Explain the dependency name for the Gradle Wrapper (#1)

* Updated `dependabot`'s docs to add `Gradle Wrapper`

* Explain the dependency name for the Gradle Wrapper

* Reword

---------

Co-authored-by: Guillermo Mazzola <gmazzo65@gmail.com>

Author: 2 people

data/reusables/dependabot/supported-package-managers.md

@@ -122,7 +122,7 @@ For more information about using {% data variables.product.prodname_dependabot_v
 
 {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files:
 * `build.gradle`, `build.gradle.kts` (for Kotlin projects)
-* `gradle/wrapper/gradle-wrapper.properties` (for the Gradle Wrapper)
+* `gradle/wrapper/gradle-wrapper.properties` (for Gradle wrapper)
 * `gradle/libs.versions.toml` (for projects using a standard Gradle version catalog)
 * `gradle.lockfile` (for projects using Gradle dependency locking)
 * `gradle/wrapper/gradle-wrapper.properties` (for the Gradle Wrapper)
@@ -135,6 +135,7 @@ For {% data variables.product.prodname_dependabot_security_updates %}, Gradle su
 > [!NOTE]
 > * When you upload Gradle dependencies to the dependency graph using the {% data variables.dependency-submission-api.name %}, all project dependencies are uploaded, even transitive dependencies that aren't explicitly mentioned in any dependency file. When an alert is detected in a transitive dependency, {% data variables.product.prodname_dependabot %} isn't able to find the vulnerable dependency in the repository, and therefore won't create a security update for that alert.
 > * {% data variables.product.prodname_dependabot_version_updates %} will, however, create pull requests when the parent dependency is explicitly declared as a direct dependency in the project's manifest file.
+> * When updating the Gradle Wrapper, {% data variables.product.prodname_dependabot %} uses `gradle-wrapper` for the dependency name.
 
 ### Helm Charts