* Add checkbox to create vmbox on user creation form
* Use waterfall flow for user creation
* Extract user create api call to new function
* Create vmbox only if requested
* Rename view data property to create vmbox
* Fix waterfall callbacks for user creation flow
* Add translations
* Refactor code and remove vmbox from callflow
* Do not show VMBox row field if there is none for user
* Do not create VMBox at usersSmartUpdateVMBox, if user has none
* Add gittatributes to use default line ending behavior
* Apply suggestions according to code review
* Code refactor according to review
* Move sub-module templates in their own `views` folder
By using `getTemplate()` we can specify which sub-module a template is
related to, enabling this behavior.
The templates names were shortened by stripping the name of their
sub-module from it since they are stored under their sub-module folder.
String templates are created using `getTemplate()` instead of
`monster.template()` that we are trying to depreciate.
* Only use `getTemplate()` for both regular and string templates