Job `binaries` can timeout in community fork pipelines

Description

The single binaries job is now responsible for compiling and cross-compiling binaries for every OS/ARCH combo supported by the runner. In the canonical repo, this job is tagged to execute on larger hardware, and the job runs rather quickly. In the community fork, the job runs on modest hardware, and can timeout and fail after 60 minutes.

Proposal

Updates should be made so that community fork pipelines can reliably complete successfully. Two separate routes were initially discussed, though these shouldn't be considered as the only possible fixes:

1. Constraining the amount of work done for community fork pipelines by building only linux/amd64 artifacts.
2. Improving the performance of the full build via better go build cache utilization.

Links to related issues and merge requests / references

[1] https://gitlab.com/gitlab-community/gitlab-runner/-/jobs/8792444307