Moving child nodes around should be calculated towards the autosave threshold

When overwriting nodes using sysview import, filevault moves child nodes and properties temporarily under temporary nodes. Depending on the number of child nodes, this may affect the size of changes in transient space, and is currently not considered when deciding when to save a snapshot.

Proposal: when doing node stashing, the # of child nodes moved around should be added to the number of operations.