Chore/remove velocity

[runspired]

This PR removes velocity usage. For the most part, this is a seamless removal

• Remove velocity transitions
• Remove velocity import and version test
• Remove velocity based animation primitives
• Alter Growable Mixin to not require velocity

TODO:

• Amend Demo Site (Demos should stay either with liquid-fire proper or with liquid-fire-velocity).
• Fix any tests that expected velocity

Questions:

• Is registering an animate function with a specific API on the liquid-fire-transitions service the way to approach liquid-fire-core's need for an animate function within Growable (@ef4 states no, changeWidth changeHeight api or similar would make more sense)
• Where does the velocity based demo site belong (I believe it belongs with liquid-fire proper)
• Do we remove explode (this is not velocity backed, so where does it belong here?) (@ef4 states it belongs here)

[runspired]

Related PR to remove core modules in liquid-fire-velocity: ember-animation/liquid-fire-velocity#1

[ef4]

Is registering an animate function with a specific API on the liquid-fire-transitions service the way to approach liquid-fire-core's need for an animate function within Growable?

animate is probably too fat and nebulous of an API. It's a very thin wrapper over velocity and can go in liquid-fire-velocity.

We can make something more specific to support growable. Maybe each animation library needs to implement changeWidth and changeHeight transitions that we can use internally.

[runspired]

@ef4 that makes a lot of sense to me, would they be required to be registered on liquid-fire-transitions ?

Or would they be expected to be in a certain place in app/utils which could then be imported by the service or an initializer or some such?

[ef4]

They can be regular transitions, no need for a special API.

[runspired]

doh