CURATOR-33 recursive TreeCache recipe

Worth doing more than just tree-order on re-sync but also giving zkId order? Probably not since I can think of edge cases where interleaved creations and deletions would cause pure mzkid ordering to conflict with tree order...