Fix CI cache problems

[athoscouto]

No description provided.

[haaawk]

Why are you removing goreleaser? I think both are useful.

[athoscouto]

Originally we just used go.yml.

But it always failed because of conflicts when we restored the cache.

This resulted in the errors you see above and also on a red status badge.
That is why @gris changed it to goreleaser.yml a few days ago.

I think a CI badge makes more sense. Meaning that the "last CI run was successful for this project".
I don't see much value in a badge saying "the last release was successful". But I also don't oppose having it.
Let me know if you still want to keep gorereleaser badge and I'll add it back. @gris let me know what you think as well.

[gris]

Makes a lot of sense! Thanks for spotting that

[haaawk]

LGTM. Is cache really useless in self hosted runners? Is it because we don't clean up the runners between CI runs?

[athoscouto]

@haaawk I think so. I was reading issues on setup-go repo to understand what was the problem here and came across this.
It is also a bit harmful since we transfer that huge amount of data (300MB+) on every run and it resulted in errors that made our badge look broken.