View animation fixes

So this is proving to be harder than I thought. The initial prototype worked but the the motion ui libraries don't seem to do well and there might be a need for angular specific motion classes.

Current issues:

- [x] adding an animation and activating it is "instant", meaning that the element does not have time to reach its initial state. - a timeout helped alleviate this problem. However, using proper animations instead of transitions may be a better alternative.
- [x] because of that, the element may falsely animate either to its end state or initial state from its current state.
- [x] animating out sometimes leaves the element on the page, the "transform end" or "transition end" events don't fire and/or get caught incorrectly.
- [ ] if landing on a subpage (child page) that's animated, parent animates as well (initially) but won't during page change.

Some ideas:

- [x] ~~register transition/transformation/animation event listener before adding animation classes.~~ <- no longer an issue
- [x]  check out if angular changed something since the prototype, and check ui router as well to see why things don't work as they used to. 
- [x] ~~create specific angular classes for animation~~ - no longer a good solution