Follow-up to https://github.com/coder/coder/pull/28919.
The tmpfs mount step only ran when `GOTMPDIR` was already exported, and
the only thing that exports it is `./.github/actions/setup-go-paths`,
which just `test-go-pg` uses. So on `test-go-pg-17`, `test-go-race-pg`
and `flake_go` the step printed `GOTMPDIR is not set, skipping` and
exited 0, and Go test binaries and `t.TempDir()` output stayed on the
root disk.
https://github.com/coder/coder/actions/runs/34359015069/job/102491022886
is one such run.
To fix, we'll just have the action default `GOTMPDIR` to
`${RUNNER_TEMP}/go-tmp` (the same path `setup-go-paths` uses) and export
it via `$GITHUB_ENV` before mounting. The skip path is gone, so a mount
failure now fails the step.
Worth noting that `test-go-pg`, where the mount was already active,
still stalled on
https://github.com/coder/coder/actions/runs/34481693660/job/102889890085,
with the `iostat` samples showing the disk at 100% utilisation
regardless. So I don't expect this to fix the stalls on its own, but it
at least makes all the Linux jobs behave the same whilst we chase the
underlying issue with Depot.