fix: accaddr cachefix (backport #15433)

[mergify]

I have a different case for this feature than the originally intended, in memiavl we are experimenting with zero-copy feature, where we return slices pointing to mmap-ed region to app directly, which means app must not retain the slices beyond next Commit event, because the region could be unmapped there when certain events happened. There are a few places in sdk that breaks this assumption:

• inter-block cache, this can be easily disabled, the functionalities is duplicated with memiavl internal cache or iavl's fast node cache anyway.
• the address cache, either we disable the cache at all, or we make it copy the byte slices before set to cache.
  • I've run the benchmark BenchmarkOneBankSendTxPerBlock with/without the cache, the difference is relatively small (time: +2.62%, alloc: +1.23%), that's when the cache is hit perfectly, in real world we have much more varieties in addresses.
    So I figure we can simply disable the cache, so we can enable the memiavl zero-copy feature.

is there other places that breaks the zero-copy assumption that I'm not aware of?

This is an automatic backport of pull request #15433 done by Mergify.
Cherry-pick of cdf6471 has failed:

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

You are currently cherry-picking commit cdf6471e5.
  (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/address.go
	modified:   types/address_test.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

[alexanderbez]

utACK. Summary makes sense to me, thanks @yihuang