Reads from .yo-rc.json before bower.json

First, this makes sure that at least one of the files exists. If it does, it attempts to assign the config found there to `this.cpui`, but if that config comes up empty, we give a helpful error message.
Merge branch 'master' into config-files-check
Merge branch 'master' of github.com:Fullscreen/generator-cpui into feature/config
Uses Yeoman's Config API

This drops the `yonconfig` stuff in bower.json and opts for creating and using the .yo-rc.json file via their config API.
Fixes the failing module creation

So, it turns out that `createModule()` was the culprit because it returned and _didn't_ run the callback, which is why it exited immediately and with no feedback.
Moves default config into json file

Since `this.src` always refers to the sub-generator's templates folder, we can at least be sure that the relative path is the same for each sub-generator. This was the best way I could think to get access to that path. Also removes the .save() line since .defaults() does that for us.
Reads from .yo-rc.json before bower.json

First, this makes sure that at least one of the files exists. If it does, it attempts to assign the config found there to `this.cpui`, but if that config comes up empty, we give a helpful error message.
Fixes the failing module creation

So, it turns out that `createModule()` was the culprit because it returned and _didn't_ run the callback, which is why it exited immediately and with no feedback.
Merge branch 'feature/config' of github.com:Fullscreen/generator-cpui into feature/config

Conflicts:
	lib/cpui-base.js
Reads from .yo-rc.json before bower.json

First, this makes sure that at least one of the files exists. If it does, it attempts to assign the config found there to `this.cpui`, but if that config comes up empty, we give a helpful error message.
Moves default config into json file

Since `this.src` always refers to the sub-generator's templates folder, we can at least be sure that the relative path is the same for each sub-generator. This was the best way I could think to get access to that path. Also removes the .save() line since .defaults() does that for us.
Adds generator for creating configs

If no config file (.yo-rc.json) exists, you're forced into creating one
the first time that you run `yo cpui`. It allows you to override some
defaults, with an exception of separators: I just think that's more
confusing during config setup than it is helpful. It can always be
modified later on, manually.

There's also a convention I tend to use, which is instead of using the
`self` keyword, I like to name the object what it is so that the context
is immediately clear.

Conflicts:
	lib/cpui-base.js
Changed the wording of the 'whats your module' step so that it's more clear how to use it.
Added some README details, mostly about opinions.
Update README.md

Fixes the code blocks
Finishing this tonight.
Merge branch 'feature/config' of github.com:Fullscreen/generator-cpui into feature/config

Conflicts:
	lib/cpui-base.js
Merge branch 'feature/config' of github.com:Fullscreen/generator-cpui into feature/config
Merge branch 'feature/config' of github.com:Fullscreen/generator-cpui into feature/config
Trying to move all of this into one of the base files... not entirely working though.