feat: configurable fastnode (backport #13321)

[mergify]

This is an automatic backport of pull request #13321 done by Mergify.
Cherry-pick of 412e2fc has failed:

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

You are currently cherry-picking commit 412e2fc86.
  (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/mock/store.go
	modified:   server/start.go
	modified:   simapp/simd/cmd/root.go
	modified:   store/cache/cache_test.go
	modified:   store/iavl/store.go
	modified:   store/iavl/store_test.go
	modified:   store/iavl/tree_test.go
	modified:   store/prefix/store_test.go
	modified:   store/rootmulti/proof_test.go
	modified:   store/types/iterator_test.go
	modified:   store/types/store.go

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	both modified:   CHANGELOG.md
	deleted by us:   fuzz/tests/store_internal_proofs_createnonmembershipproof_test.go
	both modified:   go.mod
	both modified:   go.sum
	both modified:   server/config/config.go
	both modified:   server/config/toml.go
	deleted by us:   simapp/go.mod
	deleted by us:   simapp/go.sum
	both modified:   store/rootmulti/store.go
	deleted by us:   tests/go.mod
	deleted by us:   tests/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]

This is at the wrong place, moving in next backported PR.