ci: drop cache: setting in setup-go/setup-node

`cache: true` (setup-go) and `cache: pnpm` (setup-node) make the
actions push and pull tarballs through the Gitea Actions cache
service at 192.168.0.222:43513. That endpoint currently does not
answer, so every workflow burns minutes per run on reserveCache
retries before the action gives up.

In host-mode the real caches live under the runner user's $HOME
(~/go/pkg/mod, ~/.cache/go-build, ~/.local/share/pnpm,
~/.cache/ms-playwright) and persist between jobs without any
actions/cache plumbing. Switching cache: off avoids the zombie
retries and uses the local disk caches the runner already has warm.

Reviving the cache service is a separate TODO. Until then this is
the simpler and faster baseline.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.gitea/workflows/go-unit.yaml

@@ -46,7 +46,13 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          cache: true
+          # `cache: true` here pushes/pulls archives through the Gitea
+          # Actions cache service at 192.168.0.222:43513. That endpoint
+          # currently does not answer, and the action wastes minutes
+          # per run on reserveCache retries. In host-mode the real
+          # caches live in $HOME (~/go/pkg/mod, ~/.cache/go-build) and
+          # persist between jobs without any actions/cache plumbing.
+          cache: false
 
       - name: Run Go tests
         # client/ is the deprecated Fyne client; excluded from CI per