Refactor: Transition dependencies

List of potential Transition dependencies and gotchas

Assumption is, if we remove transitions out of changePage(), what could bite?

---

$.mobile.urlHistory.pageTransitionQueue

Array, queue to hold simultanious page transitions, referenced in two areas of changePage()

$.mobile.urlHistory.isPageTransitioning

Boolean, indicates whether or not page is in process of transitioning, referenced in two areas of function changePage(), always in close conjunction with $.mobile.urlHistory.pageTransitionQueue.

Potential to gather and extract some of the internal utility functions

function removeActiveLinkClass( forceRemoval ) https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L275

$.fn.animationComplete, the animation complete callback https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L284

Transition-related class-setting code between L501 and L530, including the pageChangeComplete() call.

See https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L500

defaultTransition() call, L563

https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L563

transitionPages() calls buried in the if(){...} else {...} that starts on line 566

https://github.com/jquery/jquery-mobile/blob/master/js/jquery.mobile.navigation.js#L566