[Bug]: ChangeAwareList incorrectly consolidates clears

[JakenVeina]

Describe the bug 🐞

ChangeAwareList<T>.CaptureChanges() contains logic to consolidate separate remove changes together to form a Clear operation, if it detects that the collection is empty upon capture. This logic produces invalid changesets, under some circumstances.

1. Non-removal changes, such as Refresh that occurred since the last capture get ignored, which could arguably be a desirable behavior, since refreshing an item is pointless if it's soon-to-be removed. Personally, I think one could also argue this is an assumption we shouldn't make.
2. Items can appear in duplicate, within the produced Clear changeset, which I think is much more problematic. Downstream consumers that seek to actually inspect removed items, for post-processing, seem likely to rely on the the idea of only post-processing each item once.

Step to reproduce

var uut = new ChangeAwareList<int>();

uut.AddRange(new[] { 1, 2, 3, 4, 5 });
uut.CaptureChanges();

uut.RefreshAt(2);
uut.RemoveAt(1);
uut.Clear();

var result = uut.CaptureChanges();

Here we can see that result does not include a Refresh for item 3, and the Clear lists item 3 twice.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.