build: add goreleaser action for streamlined releases

[particledecay]

Hello, I would like to make Gametime a better place by contributing the following code:

Feature/bug description

Add goreleaser for creating GitHub releases with cross-platform binaries upon tagging the repo.

This is how I decided to implement/fix it

I added Goreleaser to the project. It is a tool that automates the process of releasing Go binaries. It creates GitHub releases with cross-platform binaries upon tagging the repo.

I chose this over Google's slightly more automated release-please-action because this repo doesn't strictly conform to Conventional Commits, so I'm not sure what would happen exactly with semantic version bumps and changelogs.

This supports the following OSes:

• Linux
• MacOS
• Windows

... and will build binaries for various architectures.

What does this change affect? (What can this break?)

It affects strictly the build process, so nothing in particular should break (current build artifacts are opinionated).

How has this been tested

It hasn't.

Observability

Before opening a PR consider whether you have added sufficient observability, do you need to add any datadog additional metrics or spans?

• Do your metrics follow the naming conventions?

How will this change be monitored

[particledecay]

Based on PLT-157, there's already apparently a ticket for using release-please-action, hmm... @davekonopka do you think this would conflict with that? I'd prefer to use release-please-action but don't think it's a requirement for this repo. What do you think?

[particledecay]

Confirmed with @davekonopka that this wouldn't conflict. While release-please-action does more and seems promising, it's more dependent on following Conventional Commit standard, which only Platform's repos do at the moment.