`replace` avoid writing aggregates up the tree

If you `replace` a key to the same or a similar key, and the sum doesn't change, we shouldn't write aggregates all the way up the tree. The counts and sums aren't changing near the top of the tree; just near the bottom. But currently we update the aggregate to remove the item and then add it back, which causes a write which can conflict with queries and other mutations