Consider `Tombstone` trait for `Diff`

In accumulating up differences, we are often lucky and they add up to zero, and we can discard the result. In some cases, mainly tombstones, we end up with something we'd like to discard (the tombstone) but which we can only do once we are sure that it has served its purpose (clobbering preceding diffs).

It seems plausible that we could inform the diff instances when they have been merged into to the oldest batch, which would imply that there would be no further updates before them. For example, there could be a tombstone(&mut self) method that gets invoked in this setting, whose implementation is by default empty (for all current implementations) but which gets called after forming each diff in the last layer. This would give tombstone diffs the opportunity to collect themselves and vanish, and would probably substantially simplify the programming of "upsert" diffs.

Very much just a musing at this point, not knowing much about the trade-offs here.

cc: @ruchirK

No files or tests are named. Start by locating the diff instances, the merge path into the oldest batch, and the final-layer diff formation; then assess whether a tombstone callback can be added without breaking existing implementations. Done would require an agreed design and concrete behavior for tombstone diffs, which the issue does not yet specify.