Please address the comments from this code review:

## Overall Comments
- The new generic `go-build-v1-` restore key removes the `GOARCH`/`TAG` scoping, which may cause incompatible cache reuse across Go versions or other tag changes; consider including at least the Go version (or equivalent) in this fallback key to avoid subtle build issues after upgrades.
- With the removal of `with: save: false` in the workflows, the behavior now depends on the default for `inputs.save` in `cache-go-dependencies`; double-check that the default matches the intended "save on master only" semantics for all callers to avoid unexpectedly writing caches on non-default branches.

## Individual Comments

### Comment 1
<location> `.github/actions/cache-go-dependencies/action.yaml:46` </location>
<code_context>
-        restore-keys: go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-
+        restore-keys: |
+          go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-
+          go-build-v1-

     - name: Cache Go Build (restore)
</code_context>

<issue_to_address>
**suggestion (bug_risk):** Consider whether the generic `go-build-v1-` restore key could lead to suboptimal or incorrect cache reuse across jobs/architectures.

This broader restore key allows caches from other jobs, architectures, or Go versions to be reused, which can both reduce cache effectiveness (due to mismatches) and introduce subtle, hard-to-debug issues from stale artifacts. Consider scoping the fallback key by at least GOARCH (e.g. `go-build-v1-${{ steps.cache-paths.outputs.GOARCH }}-`) and possibly Go version so fallback restores stay within compatible builds.

Suggested implementation:

```
        key: go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-${{ steps.cache-paths.outputs.TAG }}
        restore-keys: |
          go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-
          go-build-v1-${{ steps.cache-paths.outputs.GOARCH }}-

```

```
        key: go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-${{ steps.cache-paths.outputs.TAG }}
        restore-keys: |
          go-build-v1-${{ github.job }}-${{ steps.cache-paths.outputs.GOARCH }}-
          go-build-v1-${{ steps.cache-paths.outputs.GOARCH }}-

```

If you want to further scope by Go version, you can:
1. Add an output like `GOVERSION` in `cache-paths` (or another prior step), and
2. Extend the fallback key to include it, e.g. `go-build-v1-${{ steps.cache-paths.outputs.GOARCH }}-${{ steps.cache-paths.outputs.GOVERSION }}-`.
Ensure that `GOVERSION` is stable and accurately reflects the toolchain version used for the build.
</issue_to_address>