deps: upgrade capability to sdk v0.50 and remove ibc-go dependency (backport #4068)

[mergify]

This is an automatic backport of pull request #4068 done by Mergify.
Cherry-pick of 49cdfc5 has failed:

On branch mergify/bp/capability/release/v1.0.x/pr-4068
Your branch is up to date with 'origin/capability/release/v1.0.x'.

You are currently cherry-picking commit 49cdfc5f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   modules/capability/keeper/keeper.go
	modified:   modules/capability/keeper/keeper_test.go
	modified:   modules/capability/simulation/genesis.go
	modified:   modules/capability/simulation/genesis_test.go
	modified:   modules/capability/types/types.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   modules/capability/capability_test.go
	both modified:   modules/capability/genesis_test.go
	both modified:   modules/capability/go.mod
	both modified:   modules/capability/go.sum
	both modified:   modules/capability/module.go
	both modified:   modules/capability/simulation/decoder_test.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[damiannolan]

build issues? 🤔 not on my machine -_-

[DimitrisJim]

oh, we'd need to backport #3851 here too for e2e failures, just seeing how old the branch we're backproting into is

[damiannolan]

oh, we'd need to backport #3851 here too for e2e failures, just seeing how old the branch we're backproting into is

oh cool, do you think you could slap the new label on that PR to get a backport going? Any idea if this could be why we're seeing build errors in CI for unsafe.String etc usage in transitive deps?

edit: these builds were passing on PR to main https://github.com/cosmos/ibc-go/actions/runs/5544957269/jobs/10123169873 but as soon as merged it failed to build.

[DimitrisJim]

Any idea if this could be why we're seeing build errors in CI for unsafe.String etc usage in transitive deps?

I wouldn't have thought so tbh, one is a failure during runtime after the binary has been successfully built, the other is a build error.

But I also can't get it to repro locally.

[DimitrisJim]

I think it's using 1.19 somehow, workflows haven't been updated to point to 1.20? edit: yea, capability workflow is using 1.19, I'd assume that was it.

And these functions were added in 1.20 https://pkg.go.dev/unsafe#StringData

[damiannolan]

I think it's using 1.19 somehow, workflows haven't been updated to point to 1.20? edit: yea, capability workflow is using 1.19, I'd assume that was it.

And these functions were added in 1.20 https://pkg.go.dev/unsafe#StringData

damn, if only I saw your comment sooner, I just came to the same conclusion! haha

[damiannolan]

Looks good to go now! Thanks for your help @DimitrisJim ❤️