Split goreleaser config file

[TylerHelmuth]

This PR adds a distribution-specific .goreleaser.yaml file to each distribution and updates the ci to use these specific file.

In the next PR I'll remove the auto-generated code, update the makefile, and remove the .goreleaser.yaml file that is at the root.

Related to #429
Closes #487

[jpkrohling]

Before approving, let's discuss whether we are ready to remove the Go code that generates the goreleaser files: removing that code generator means we'll have to maintain those two YAML files. Adding cosign, for instance, would have required adding the same things on the two files.

I'm fine if we have a reason not to generate the goreleaser files, such as significant differences between the distributions.

[cpanato]

lgtm

[TylerHelmuth]

@jpkrohling i think we could do the same approach you've done in your repo and auto generate the separate files. I was planning to do that in a future PR.

[jpkrohling]

Can you confirm how to run this locally? I tried the following, but it failed:

> goreleaser --snapshot --clean 
  • starting release...
  ⨯ release failed after 0s                  error=yaml: unmarshal errors:
  line 1: field partial not found in type config.Project

I also tried something closer to what we have in the CI files, but also failed:

> goreleaser --snapshot --clean --skip-sign --skip-sbom --timeout 2h --split --id otelcol
  ⨯ command failed                                   error=unknown flag: --split

[cpanato]

if you are using the more up-to-date goreleaser you can update the --skip flags to use --skip=sign,sbom

[TylerHelmuth]

@jpkrohling I've never tried to run locally. We use goreleaser-pro in the repo and I don't have access locally. A lot of the features we use are pro features.

Split and partial are specifically pro: https://goreleaser.com/customization/partial/

[jpkrohling]

There's still a .goreleaser at the root of the repository and needs to be removed.

stale review