Fix heavy dependence on the DOM for carousel transition information

[wesleycho]

See discussion in #4325 - this exposes a heavy dependence on the DOM structure, which defies the custom template possibilities.

This needs to be untangled in a clean way to avoid the heavy dependence and part of the limitations of .animation - might need to store all the slides for a carousel in a model using $$multiMap.

[chrisirhc]

The NO_TRANSITION hack was there because there was no way to use $animate.enabled as a getter (the getter was added in Angular 1.4). Now that that's no longer true, we can remove the usage of .data . Now if we're updating the dependency to Angular 1.4, it can instead use $animate.enabled on itself, as $animate.enabled gets inherited by children.

[wesleycho]

Thanks for that - that is exactly the info I needed!