Noop batch causes storage events to fire twice

[BitPhinix]

While going further down the history rabbit hole, I discovered another issue, this time not related to history, and I'm still trying to figure out the best approach to fix it.

When performing changes inside batch that are essentially noops (i.e., inserting and immediately removing the same list item), we fire storage events for those noop changes twice (once for the local change and once when we receive the "confirmation ops" from the server).

This stems from how we filter out remote updates when handling remote changes: We ignore all operations that don't cause a change. This works fine for most cases, but not when we insert and remove the same item in the same batch because that batch will always cause an update (inserting and removing the item).