Don't use "fast node storage" in IAVL MutableTree
From what I've observed so far most of the queries we make end up not using the "fast nodes," (because we mainly read "committed" data) meaning they mainly exist to take up space and to slow down snapshot import greatly. This might be reverted if further evidence ends up proving this was a bad idea.