Self hosted windows 11 runner throws warning, with cache enabled in post step [Bug]

Post job cleanup.
UV_CACHE_DIR is already set to C:\Users\mythi\AppData\Roaming\uv\cache
UV_PYTHON_INSTALL_DIR is already set to C:\Users\mythi\AppData\Roaming\uv\python
Pruning cache...
(node:18612) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
C:\actions-runner\ZedfestModdingKitWorkFolder\_tool\uv\0.10.4\x86_64\uv.exe cache prune --ci --force
Pruning cache at: C:\Users\mythi\AppData\Roaming\uv\cache
Removed 18588 files (86.1MiB)
Including uv cache path: C:\Users\mythi\AppData\Roaming\uv\cache
"C:\Program Files\Git\usr\bin\tar.exe" --posix -cf cache.tgz --exclude cache.tgz -P -C C:/actions-runner/ZedfestModdingKitWorkFolder/ZedfestModdingKit/ZedfestModdingKit --files-from manifest.txt --force-local -z
/bin/sh: line 1: gzip: command not found
/usr/bin/tar: cache.tgz: Cannot write: Broken pipe
/usr/bin/tar: Child returned status 127
/usr/bin/tar: Error is not recoverable: exiting now
Warning: Failed to save: "C:\Program failed with error: The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2
uv cache saved with key: setup-uv-2-x86_64-pc-windows-msvc-windows-11-3.12.12-pruned-144bf72b5f6c480977682dda78a71f2938ca950e1d59aa7d1d6ea5bddcb82223

I am not sure if there is something extra I should install, or if the tool has not accounted for this instance.
It is a bit up in the air to it being a self hosted runner. I am not 100% sure if the same issue would occur otherwise

this is the yml file
```
name: example_map_release

on:
push:
branches:
- main
workflow_dispatch:

jobs:
make_release:
name: example_map_release
runs-on: [self-hosted, windows, x64]

steps:
- uses: actions/checkout@v6

- name: Install uv with caching enabled
uses: astral-sh/setup-uv@v7
with:
enable-cache: true

- name: Install the project with all dev dependencies
run: uv sync --locked --all-extras --dev

- name: Install tempo-cli
run: uv tool install git+https://www.github.com/Tempo-Organization/tempo-cli

- name: Run tempo-cli mod release creation command
run: tempo_cli run full_run_all --settings_json ".tempo.json"
```

Start with the workflow's setup-uv@v7 step and its post-job cache-save log on the self-hosted Windows runner. Check whether the runner's Git installation provides the gzip command used by tar, and compare the behavior with a non-self-hosted Windows runner if available. Done means the cache is saved without the gzip, broken-pipe, or failed-to-save warnings.

Written by the indexing model from the issue text.