feat(app): Update post handlers to incorporate the runMsg success bool (backport #13940)

[mergify]

This is an automatic backport of pull request #13940 done by Mergify.
Cherry-pick of 551e8f9 has failed:

On branch mergify/bp/release/v0.47.x/pr-13940
Your branch is up to date with 'origin/release/v0.47.x'.

You are currently cherry-picking commit 551e8f9eb.
  (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:   baseapp/baseapp.go
	modified:   baseapp/options.go
	modified:   docs/docs/core/00-baseapp.md
	modified:   testutil/mock/types_handler.go
	modified:   types/handler.go
	modified:   types/handler_test.go
	modified:   x/auth/posthandler/post.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CHANGELOG.md

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

[julienrbrt]

I think it's a regression of #13983 to remove this.

[julienrbrt]

If we merge this we need to backport #14613 too.

[fedekunze]

yes, let's backport both