deps: bump SDK v0.50.1 (backport #5038)

[mergify]

This is an automatic backport of pull request #5038 done by Mergify.
Cherry-pick of 27b8afa has failed:

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

You are currently cherry-picking commit 27b8afab.
  (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)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   CHANGELOG.md
	both modified:   e2e/go.mod
	both modified:   e2e/go.sum
	both modified:   go.mod
	both modified:   go.sum
	both modified:   modules/apps/27-interchain-accounts/host/keeper/relay_test.go
	deleted by us:   modules/apps/callbacks/go.mod
	deleted by us:   modules/apps/callbacks/go.sum
	both modified:   modules/capability/go.mod
	both modified:   modules/capability/go.sum
	both modified:   modules/capability/module.go

no changes added to commit (use "git add" and/or "git commit -a")

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]

I have removed the e2e directory on this release branch and other diffs associated with strictly ibc-go and callbacks.

There is currently an unnecessary amount of workflows running on this branch with old stale code.

What do people think about reducing the number of workflows running on this branch to be capability only? All that is required is build, test, lint I suppose.

[colin-axner]

Thank you @damiannolan 👑

[colin-axner]

Would be nice if we could reference e2e's on main as a way to run e2es (future suggestion)

[DimitrisJim]

What do people think about reducing the number of workflows running on this branch to be capability only? All that is required is build, test, lint I suppose.

ibc-go imports capability so it does make sense to run tests for it?

[damiannolan]

ibc-go imports capability so it does make sense to run tests for it?

Yes, but ibc-go would still be importing a specific tag of x/capability and not these PRs. And having a local pin would just be more overhead.
All ibc-go code on this branch is effectively stale as it hasn't been maintained in-sync with this release branch.

I am confident that tagging this and importing in ibc-go would be completely fine, we could temporarily point ibc-go to the head of this branch and run tests before tagging, but the unit tests in this module were given a bit of attention such that we could rely on them as a safeguard.

[chatton]

LGTM