feat: build Ryuk using goreleaser

[mdelapenya]

What is this PR doing?

It adds goreleaser as build tool to cross-build Ryuk in all supported platforms:

Binaries

• linux/amd64
• linux/arm64
• linux/ppc64le
• linux/s390x
• darwin/amd64
• darwin/arm64
• windows/amd64

Dockers

• linux/amd64
• linux/arm64
• linux/armv7
• linux/ppc64le
• linux/s390x
• windows/amd64 2019lts
• windows/amd64 2022lts
• latest and the current tagged version will be multi-arch

For that, we will need to build each platform on its own GH worker, and finally create the single multi-platform manifest in the very same worker that created the image. For that, an initial stage pushing the first manifest must be done beforehand.

graph TD
    A[Build Ryuk] -->|ubuntu-22.04| B(Build linux/amd64)
    B --> |ubuntu-22.04| C(Create manifest: linux/amd64)
    D[GH Workers] --> |ubuntu-22.04| E[Rest of linux images]
    C --> |Cross-Build| D
    D -->|windows-2019| F[lts2019]
    D -->|windows-2022| G[lts2022]
    E --> H(Annotate the manifest)
    F --> H
    G --> H

Loading

As seen in the diagram, we need to first create a manifest (build+push), i.e. for linux/amd64, in order to create an initial image where to append the rest of manifests in parallel, and once it finishes, build and annotate the rest of the linux and the windows versions.

Each OS-stage will have its own goreleaser config file, so that it knows what to build

Why is this important?

Cross-build Ryuk in a simple, consistent and standard way

[HofmeisterAn]

Can we pass arguments to the GoReleaser YML files?

[HofmeisterAn]

Dunno, if we need to think about it, but what happens if one OS fails to push the image? We clean it up afterwards by hand?

[mdelapenya]

This is something to evaluate, and probably have a rescue condition: if any of the stages fail (create the initial linux/amd image > create the rest of linux | create windows2019 | create windows2022), should we remove the image from the registry? IIRC it was super hard in the past to remove an image from a registry using CLIs/APIs, not sure if nowadays it's possible

[mdelapenya]

Checking with the authors of goreleaser here: goreleaser/goreleaser#3314 (reply in thread)

[mdelapenya]

We are going to test this like this:

• create a baseline branch, goreleaser
• merge this PR on that baseline branch
• use a fork (e.g. @mdelapenya) to update the manifests to push the docker images to a different Docker namespace
• update the goreleaser GH action to listen to pushes in the goreleaser branch to test incremental changes