feat: More flexibility for CacheMultiStoreWithVersion

[catShaark]

Description

Closes: cosmos/gaia#2313

The gaia v9 upgrade causes node to errors out when querying historical states before the upgrade. This is because we added a new module store in the upgrade which is the provider module store. Thus, every times we load the multi store for querying at a height prior to the upgrade, we try to load the provider module store and fail since it has not existed before the upgrade.

I make changes to CacheMultiStoreWithVersion so that if we fail to load any module store at a given height, we check if that module store has existed at that height or not (using getCommitInfo()), we can ignore the error if the store hasn't existed at that given height.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[tac0turtle]

Hey, lets make this pr against main if its needed. Unfortunately, 0.45 is only for security upgrades going forward. This is inline with our release process. We wont be able to accept this pr.