feat: add config iavl-lazy-loading to enable lazy loading of iavl store (backport #14189)

[mergify]

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

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

You are currently cherry-picking commit b266522c8.
  (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/options.go
	modified:   server/config/config.go
	modified:   server/config/toml.go
	modified:   server/mock/store.go
	modified:   server/start.go
	modified:   store/iavl/store.go
	modified:   store/iavl/tree.go
	modified:   store/rootmulti/store.go
	modified:   store/types/store.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   CHANGELOG.md
	both modified:   cosmovisor/go.sum
	both modified:   go.mod
	both modified:   go.sum
	both modified:   server/util.go
	deleted by us:   simapp/go.mod
	deleted by us:   simapp/go.sum
	deleted by us:   store/go.mod
	deleted by us:   store/go.sum
	deleted by us:   tests/go.mod
	deleted by us:   tests/go.sum
	deleted by us:   x/nft/go.mod
	deleted by us:   x/upgrade/go.mod
	deleted by us:   x/upgrade/go.sum

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]

utACK. About the explanation, maybe it is something to mention in the release notes at release.