New package structure

[ognen]

As it becomes apparent that parts of the framework, need to be useful in a Node environment, it becomes necessary to restructure the packages a bit better. Additionally, we are gearing up towards a rename, so we could use the occasion to introduce the new package structure.

I think the new package structure should look like:

• config -- as is now, no change
• components -- as is now
• system -- the system/subsystem framework extracted into a separate module:
  • the System no-longer offers a redux store but is a simple micro DI framework (will need some refactoring)
• core -- the future core package contains the following features (usable from all supported environments):
  • data, registry, zip
  • logging internals
• transforms -- the transform, enrich, enhance subsystems, allowing registration and access to transforms. Can be used in React, RN, Node
• app -- this package contains
  • store (a new subsystem that provides the redux-store, dispatch and middleware handling)
  • ui, read, effect, update subsystems
• classic a backwards compatibility package that users of girders-elements initially switch to.

Furthermore, the core package's kernel should be re-considered within a koa-drven multi-phase scenario. What primitives do we add there?

@bevkoski, @andon thoughts?

[bevkoski]

I would put transform, enhance and enrich in a single package named transformation or transforms.

Regarding the last package, I would definitely go with the name app rather than react.