fix($animate): ensure that class-based animations only consider the most recent DOM operations

Prior to this fix $animate would maintain a count of each time a class was
added and removed within $animate. With this fix, $animate instead only cares
about the most recent class times that the classes were added and/or removed
and it will only remember a total of one addClass or removeClass operation per
className.

```
// before
addClass    => 1
removeClass => 0
addClass    => 1
addClass    => 2
addClass    => 3
removeClass => 2
removeClass => 1
// since 1 > 0 then this will cause an addClass animation

// now
addClass    => 1
removeClass => 0
addClass    => 1
addClass    => 1
addClass    => 1
removeClass => 0
removeClass => -1
// since 1 < 0 then this will cause an removeClass animation
```

Closes #8946
However, regardless of the performance, frankly the object case is just way simpler, and resolveElementClasses is basically doing it anyways --- so it's probably better to just do it