Refactor UserModule with composer

[dragoonis]

We need to have our modules in our vendor folder to publish new changes to users with little to no interruption to their ppi application.

As a result, packagist package "ppi/user-module" will be installed to ./vendor/ppi/user-module/

All the code we currently have in the skeleton app will be moved to the vendor folder, and the files will remain in the skeletonapp, but they will extend the vendor class.

module 'PPIUserModule' will be in ./vendor/ppi/user-module/.
module 'UserModule' will be in ./modules/ppi/UserModule/

<?php
namespace UserModule\Controller;

use PPIUserModule\Controller\Index as BaseController;

class Index extends BaseController {}

The class body will be entirely empty, and the app developer can override the 'showAction' or 'deleteAction' as necessary.

[dragoonis]

Tagging v2.1 milestone on this, it's important that we look at it once more trivial and quick-n-easy tasks have been taken care of in 2.1

[vitorbrandao]

@dragoonis Do you think this will arrive on time for 2.1? Maybe move it for 2.2?

[dragoonis]

It will come shortly after 2.1 for sure, it's a userland module so it will be launched just after we launch 2.1