gcsLookup cache is not flushed in No-Op animator.

[bennadel]

Right now, the animation process only flushes the gcsLookup and the gcsStaggerLookup cache in the request animation frame callback. This creates an interesting edge-case in which a no-op animation on a given element will prevent a subsequent animation from taking place. I've tried to outline my findings here:

http://www.bennadel.com/blog/2884-possible-bug-empty-animations-are-cached-in-angularjs-1-4.htm

You can fix this by flushing the cache within the closeAndReturnNoopAnimator() function; but, I am not familiar enough with the animation process to know if this is a good idea or if it will have unforeseen consequences in more complex animations.