feat: Add skipFastStorageUpgrade to MutableTree to control fast storage upgrade

[adu-crypto]

type MutableTree struct {
	*ImmutableTree                                     // The current, working tree.
	lastSaved                *ImmutableTree            // The most recently saved tree.
	orphans                  map[string]int64          // Nodes removed by changes to working tree.
	versions                 map[int64]bool            // The previous, saved versions of the tree.
	allRootLoaded            bool                      // Whether all roots are loaded or not(by LazyLoadVersion)
	unsavedFastNodeAdditions map[string]*fastnode.Node // FastNodes that have not yet been saved to disk
	unsavedFastNodeRemovals  map[string]interface{}    // FastNodes that have not yet been removed from disk
	ndb                      *nodeDB
	skipFastStorageUpgrade   bool // If true, the tree will work like no fast storage and always not upgrade fast storage

	mtx sync.Mutex
}

Add the skipFastStorageUpgrade field to MutalbeTree.
If skipFastStorageUpgrade is true, neither Load(), LazyLoadVersion(), LoadVersion() nor LoadVersionForOverwriting would try to upgrade fast storage when loading the tree.
This is needed for archive nodes with extremely big db to avoid taking unacceptable long time to upgrade the fast storage

[tac0turtle]

left one comment

[tac0turtle]

LGTM, we will have to push this to a branch without the cosmos-db changes.

[adu-crypto]

LGTM, we will have to push this to a branch without the cosmos-db changes.

is this not compatible with cosmos-db? which branch do you suggest pushing to?

[tac0turtle]

I can handle this part, will start right when this is merged. Would like to get one more review before then