build: update 99designs/keyring to use cosmos fork

[clevinson]

Description

Ref: #1698

I was finally able to get the issue in #1698 reproducing locally (running https://github.com/nektos/act again).

Unfortunately, just running act on its own wouldn't quite work properly. Running the goreleaser action requires GitHub Tokens and will push binaries to GitHub release's API, etc.

Instead I ran:

• act -j release --container-architecture linux/amd64 -v
• when the process failed (due to missing GitHub tokens), I shelled into the docker container with: docker exec -it ${container_id} /bin/bash
• ran ln -s /opt/hostedtoolcache/go/1.19.4/x64/bin/go /usr/bin/go to add the go binary in my PATH
• ran /opt/hostedtoolcache/goreleaser-action/1.13.1/x64/goreleaser build --skip-before --skip-validate --help -id regen-darwin-amd64 to build the failing darwin binary

This successfully reproduced the error on goreleaser (ld having an unrecognized flag -dynamic).

After digging some more, I found cosmos/cosmos-sdk#12952 which seemed to contain some related fixes in the fork that looked similar to changes we made in our go 1.19 related patches:

https://github.com/cosmos/keyring/pull/2/files#diff-33f8fbc61d6878200e61e69725cd724475a0c9dbb73bc63fcfc913a5651764feL175-L176

I thought that I got the goreleaser building successfully after updating the 99designs/keyring replace directive (as in this PR), but on subsequent runs it seems to still be failing...

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[clevinson]

Adding these so that I could build goreleaser locally via act. Otherwise the build was hanging when running the GitHub actions locally.

[ryanchristo]

Do we still need these or was this for testing purposes?

[clevinson]

It shouldn't have any affect on CI runs of goreleaser, but local testing via act will not work without these -y flags.

I like having them checked in to code so the goreleaser setup can be used for local testing as-is. If you're OK with keeping I'd like to just keep & merge. If you prefer without then I can remove.

[ryanchristo]

LGTM. One question before merging.

[ryanchristo]

Do we still need these or was this for testing purposes?