Corrupt golang cache entries in CI

We are seeing issues on various section of the CI when using golang tools. These seems to be related to corrupted cache entries when installing/setup of golang.

A root cause has not yet been determined, but re consolidating our cache entries and being more specific with what can/can't write or use cache entries should help narrow this down. 