[Feature]: use historical tree after migrating to another tree

[tac0turtle]

Summary

in v2 we allow users to use different trees, when users migrate from v1 to v2 they can continue with iavl v1 or migrate to iavlv2. the migration to v2 uses the snapshot manager to do the migration, but it does not migrate historical information. We opted to not migrate historical information instead when the migration is completed we store the height the migration occurred at, then when a user requests data from a older version we query the old tree for that information if the node operator enables the feature.

Problem Definition

No response

Proposed Feature

store the migration height after the migration has completed, if a node operator enables historical information querying then we allow kv queries to be routed to the old tree.