As a developer I want the CLI to create working starting definitions for M6 and M5 projects, so that the CLI helps me rather then possibly confusing me.

Acceptance critiera

• 'create' commands create definitions using the corect definition style for the project, not old ones. At least:
  • should use '$type' instead of 'class'
  • dialogs should not supply actions.
  • An example of a form layout should be included.
• One installation of magnolia CLI will work for multiple projects. There is a way that the CLI knows which styule of definition to create for the project that I am currently working on.
• In one project I want to create m5 definitions for some types (like "blocks" ) and m6 for some thypes (like "components")

Use cases

• I am working on a 5.7 project. I want the CLI to use the prototypes for 5.7
• I am working on a 6.2 project I wasnt the CLI to use the prototypes for 6.2
• I have 2 projects on going, one of them is 5.7, one is 6.2, I want to use different prototypes depending on my project.
• I am working on a 6.2 project, but we are still using 5.7 version of Pages app.
• I am working on a 6.2 project, but we are still using 5.7 version of Stories app.

Please see discussion and other proposals here:
https://wiki.magnolia-cms.com/display/PMTEAM/How+should+CLI+handle+multiple+versions

Have a look at this closely related PR:

https://git.magnolia-cms.com/projects/BUILD/repos/npm-cli/pull-requests/131/