[WIP] Chore/make consumer

[runspired]

This PR converts liquid-fire into an addon shell around liquid-fire-core and liquid-fire-velocity.

• Remove code and tests now supplied by the other addons
• Add a blueprint to install the new addons when installing liquid-fire
• Trim dependencies that were only needed by removed code
• Release the new addons
• Consume the new addons as dependencies for the demo site and testing
• Move Open PRs here to being against the appropriate new project
• Update README

Unresolved Questions

• Should the demo app stay a part of this repo (currently think yes)
• Should explode be supplied here, in core, in velocity, or in another project (liquid-fire-helpers)
• Should we / can we port issues to other projects where they belong

[runspired]

Related PRs for Tracking:

• liquid-fire-core: Chore/remove velocity liquid-fire-core#1
• liquid-fire-velocity: Chore/core removal liquid-fire-velocity#1

[ef4]

I'm not too hung up on where people file issues, it's fine if they all end up here by default, except in cases where the user digs deeper and identifies a specific repo.

Add a blueprint to install the new addons when installing liquid-fire

I don't think we need a blueprint, just an npm dependency from liquid-fire to liquid-fire-core and liquid-fire-velocity.

Should explode be supplied here, in core, in velocity, or in another project (liquid-fire-helpers)

I think in core, since it's generally useful library code that's not dependent on any specific animation library.