feat: Rework GitHub action with goreleaser

[yodamad]

Fix #27

Need to setup a GH_TOKEN on project with rights to write to plumber and homebrew-plumber for goreleaser to be able to push binaries and infos

Review and rework if needed release.yaml also

[Joseph94m]

I don't know github actions enough to evaluate this simply from reading. I need to ensure the following:

• Release lifecycle only updates patches: we want to stay in the v0.1.X for now.
• The generation and embedding of the default configuration file default.yaml in https://github.com/getplumber/plumber/tree/main/internal/defaultconfig must not be lost during this migration
• All the binary formats (windows, arm, amd, linux, macos), their checksums, names and paths must remain the same
• docker images must be pushed with 4 images: latest, 0, 0.1 and 0.1.x
• New tap formula must be pushed on every release: latest must be updated + 1 file for pinned keg version
• Use GITHUB_TOKEN instead of GH_TOKEN

[yodamad]

Almost everything you explained is covered by goreleaser (not by github actions)
I've kept the docker part you've made befire, the only point it the stuff about the configuration file (not sure to understand why it should be done)

Regarding the token, it is a secret necessary for goreleaser, i've called it GH_TOKEN, but it could BLABLA_TOKEN also

[thomasboni]

cursor review verbose=true

[cursor]

Bugbot request id: serverGenReqId_f87dfb02-130a-4320-855a-eaa5c9baeb87