Removing animations is done through accessing animations
on animator which was cleaned before the access. Fixed by
swapping order of method calls

The ~0.001 seconds lag between animations were extremely
noticeable if the duration was long.

There is no need to recalculate duration from the current state
of the view. Motion calculates it when animations is first fired off
and on resume remaining duration can be recalculated
as usual (duration - progress).

This way we no longer need CAAnimationDelegate to
listen to animationDidStop in order to update the model
and remove animation after it's done. We update the model
in advance, and system just removes the animation on completion

Also fixes animation group not removed from layer after completion

use Application.shared to keep extensions happy

Support extension

Use Application.shared to allow framework to be linked from extensions.

Fixed issue-44, view is hidden below status bar during call

Fixed issue-29, unbalanced calls to begin/end appearance transitions

Calling {begin,end}AppearanceTransition methods for modal transitions
was causing the issue since UIKit was already calling them that internally

pr-40: Fixed delegation issue, where UINavigationController and UITabBarController were incorrectly calling their delegate methods

Fixed overridden delegates were not forwarded

issue-1022: Fixed alpha issue, where alpha was being set to 1 and not respecting the initial set alpha value

updated Motion internals to remove motion only animations and handle TabBar animations when being pushed with hideBottomBarWhenPushed