Improve new module creation

[peterkeating]

Speaking with @JoeMoov2 while he was setting up a new module during some client work, we agreed that creating a new module has a bit too much "manual faffing". These are the current steps we've been taking when adding a new module:

• Create empty repo for module in Bitbucket
• Add repo as submodule into /modules/Module.Name
• Copy local orchard module files created during code gen into submodule directory
• Delete module within local Orchard modules folder
• Run grunt setup

It'll be cool if we could create a grunt task that would do all this for us, including the code generation of a module that only contains necessary files / directories. The command would look a little like the one shown below.

grunt create-module -name=Moov2.Orchard.ModuleName -submodule=git@github.com:moov2/Moov2.Orchard.ModuleName

It'll be best if the -submodule parameter was optional, in case we decide having modules as submodules isn't the best approach.