feat(workflows): add goreleaser

[stauersbol]

Simply adds goreleaser, there is a bunch of defaults and some things are locked behind their pro plan, but might not be necessarily useful things.

There could be some debate on the .goreleaser.yaml config file, but I'm all ears on that part.
It defaults to prerelease as this was a request from ayyan.

Feel free to go read through the docs at: https://goreleaser.com/customization/

[stauersbol]

looks like i forgot to setup signed commits, will have to do that

[stauersbol]

should all be signed now after amending them

[ayn2op]

https://github.com/goreleaser/goreleaser-cross

[stauersbol]

goreleaser/goreleaser-cross

yep that was the plan to use, didnt have time to look into it yesterday, plan is doing so day.

[stauersbol]

@ayn2op need you opinion on some bits, ive added comments to what im unsure about. for the most part dry-run works.

I believe there is still some configuration left and I might just nuke the custom name templating I did, as it makes the life of packagers easier on AUR and such.

[stauersbol]

I might also consider adding linux arm64 and arm64hf (in case pi users would like to use it)

[stauersbol]

alright touched the points you had @ayn2op, i also went ahead to add linux arm64 and armv7 build targets, since it could be relevant if some users of those 2 ISAs appear.

[stauersbol]

Though there is something with how changelog works, unsure how it works under CI conditions, but it may overwrite any auto generated changelog notes on a release, but it might be worth the initial try and then adjust if it does indeed overwrite

[stauersbol]

simplified the build targets in the config and also added some docs in the readme that describes goreleaser