Remove `cache-dependency-glob` examples for `setup-uv` (#14493)

See https://github.com/astral-sh/uv/pull/13163#discussion_r2063244551

docs/guides/integration/github.md

@@ -217,39 +217,6 @@ persisting the cache:
     enable-cache: true
 ```
 
-You can configure the action to use a custom cache directory on the runner:
-
-```yaml title="example.yml"
-- name: Define a custom uv cache path
-  uses: astral-sh/setup-uv@v6
-  with:
-    enable-cache: true
-    cache-local-path: "/path/to/cache"
-```
-
-Or invalidate it when the lockfile changes:
-
-```yaml title="example.yml"
-- name: Define a cache dependency glob
-  uses: astral-sh/setup-uv@v6
-  with:
-    enable-cache: true
-    cache-dependency-glob: "uv.lock"
-```
-
-Or when any requirements file changes:
-
-```yaml title="example.yml"
-- name: Define a cache dependency glob
-  uses: astral-sh/setup-uv@v6
-  with:
-    enable-cache: true
-    cache-dependency-glob: "requirements**.txt"
-```
-
-Note that `astral-sh/setup-uv` will automatically use a separate cache key for each host
-architecture and platform.
-
 Alternatively, you can manage the cache manually with the `actions/cache` action:
 
 ```yaml title="example.yml"