Handle config project fetching

[chrisdmacrae]

Config projects should not exist in c/ss. They should exist as NPM dependencies.

Something CRA does that I do not think is necessary is full-blown fork of the project for different configs.

We need two levels of abstraction:

• A build template: templates that abstract build tools to a specific configuration that are generally applicable.
• A site template: templates that abstract site generators to a specific configuration that are generally applicable.

These are bridged by three things:

• A source folder
• A dist folder
• A task runner

The task runner can execute parts of the build and site projects in the order necessary to make the interoperable.