Goals
Be able to create a new project based on a Maven Archetype
Note: This epic should be implemented as much as we can in their own module, because it will be reusable in future.

Non goals
We will only support maven archetypes, so this epic doesn't cover creating projects based another mechanisms (i.e. JHipster).

Acceptance criteria
On Global Settings, the user will be able to create and delete archetypes and also select one as default.
Those archetypes will be validated by Business Central and can only be added if BC is able to create projects based on them.
On the space settings (new space tab), user will be able to filter and add archetypes (from global settings) and select one by default.
On add project screen (under advanced options), user will able to select if they will create the new project based on archetype and select which archetype it will use from a checkbox (default archetype selected by default).

Note:

• If a space has a default archetype, all new projects will have the checkbox (create based on an archetype) marked as default. If there is no archetype defined on space, this option will be false.
• As soon as user define a global archetype as default on bc, all the new spaces will have this archetype as default.
• When user add an archetype on global settings, we will need to validate if this archetype works. If doesn't, we will not add this archetype to the list. All those archetypes will be stored in a cache and validated on BC startup, if one of the archetypes is invalid, they should be marked as invalid and not be usable on BC (added on space settings and also be the base for new projects).

[1] (for each archetype from the list, we should make sure that there is a directory on temp archetype directory ready to be cloned, if not, we should build and validate each archetype.