Use View template explicitly in controllers. Add templates to options

[visto9259]

Currently, LmcUser uses a template stack in the View Manager configuration to map controller actions to templates.
Most users will replace the provided templates to suit their UI needs. To overwrite the default templates, the use will overwrite the template map to have the View Manager use their templates.

For example, to overwrite the login template, the use will overwrite the lmc-user/user/login to point to their template file.

To make customization easier, the controller action should use named template and the named template should be in the Module Options.

For example, the login template to use should be defined by:

  'lmcuser => [
     'templates' => [
          'login' => 'lmc-user/user/login',
          /* ... */
      ],
  ],

Then, in the login action, the controller will retrieve the login template from the Module Options and set the template for the View Model instead of relying on the View Manager to inject the template.

• Add template options to LmcUser/Options/ModuleOptions with defaults refering the template map
• Modify the View Manager module configuration to define a template map.
• Modify the controller actions to use the templates from the ModuleOptions and explicitly set the template in the return View Model
• Update test cases
• Update documentation