chore: UX Mempool Tweaks (backport #15121)

[mergify]

This is an automatic backport of pull request #15121 done by Mergify.
Cherry-pick of 77660ec has failed:

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

You are currently cherry-picking commit 77660ec45.
  (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:   types/mempool/sender_nonce.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   types/mempool/priority_nonce.go
	both modified:   types/mempool/priority_nonce_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

[tac0turtle]

should remove usage of global bech32 usage

[alexanderbez]

should remove usage of global bech32 usage

This doesn't make sense IMO. Bech32 isn't going anywhere.

[tac0turtle]

should remove usage of global bech32 usage

This doesn't make sense IMO. Bech32 isn't going anywhere.

it wont be a global anymore is what im trying to say. it will be local to auth allowing app devs to define their own address encoding if they want. This would require a custom auth module

[alexanderbez]

Yeah, however we define it, it'll be wired through to the mempool via an interface or something that doesn't depend on x/auth. There are many places in the SDK that require or find Bech32 useful, so it's not just limited to mempool.

dismissing for 0.47