ConfigParser and JSON

This pull request has a module for a clean/raw data implementation.

I needed the two to be deep copies of the config and I decided to try switching the config over to a JSON file. I couldn't find a good way to create a deep copy of the config other than parsing the JSON twice without using a framework or a hacky method. One method I found was to turn the in memory config into a JSON string and then parsing that to create the deep copy, but I felt it was a bit too hacky.

The full config (with both clean/raw) isn't stored in passup at the moment. Only the clean one is stored, but we can always store both later if needed. I'm not completely happy with it, figured I'd see what you think.