Repurpose 'bolt init' to create a skeleton bolt project directory structure

[marlimox]

It would behave similarly to the git init command:

bolt init [DIRECTORY]

It would create a basic bolt project directory structure in the current or specified directory. This would add:

• A basic project.json config file in the root.
• A config/bolt directory with basic prod/test/demo configs.
• src/test/demo directories with default directory structure.
• Probably not any default source/test files, as I question their value a bit. They will never be source you actually want to keep, so it just forces people to delete them or replace them with real code. Could be convinced otherwise though, especially if you could parameterise the template with project name/namespace, etc.
• Potentially demo files could be added, such as a demo.html.

This command could check for the existence of a project.json file or config/bolt directory before running to prevent accidental re-running.

[markhibberd]

I am good with this. There is a bunch of code gen things that might come into play (independently of bolt init). For example I really want to be able to generate the karma config which is a hideous beast, and can be derived from project.json and configs.