feat: add goreleaser workflow

[yihuang]

Closes #296

Description

Add a goreleaser github action workflow.

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

---

For admin use:

• Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
• Reviewers assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[fedekunze]

this looks ok, but should we use the goreleaser action instead?

https://github.com/goreleaser/goreleaser-action
https://goreleaser.com/ci/actions/
https://github.com/cosmos/cosmos-sdk/blob/master/.github/workflows/tag.yml

[yihuang]

this looks ok, but should we use the goreleaser action instead?

https://github.com/goreleaser/goreleaser-action
https://goreleaser.com/ci/actions/
https://github.com/cosmos/cosmos-sdk/blob/master/.github/workflows/tag.yml

that looks good too, when did the RELEASE_CHANGELOG.md get generated?

[fedekunze]

when did the RELEASE_CHANGELOG.md get generated?

not sure, I'd need to dig into the release process

[fedekunze]

let's use the GitHub action as it's easier to maintain

[yihuang]

let's use the GitHub action as it's easier to maintain

done

[fedekunze]

ACK. I will wait for @khoslaventures 's review too