Split MVC related components to a separate package?

[visto9259]

Should we split LmcUser into authentication components and MVC components?

Objective:

• Have a base set of components related to authentication, entity, data mapper
• Have a separate set of components to deal with login, logout, register and other MVC actions
• This will allow for a lighter weight footprint that do not add MVC routes to the application

[visto9259]

The base component will be LmcUserCommon.

[visto9259]

Corresponding issue LmcUserCommon#2