Proposal: include real sample melody applications in this repository

[danielcaldas]

Explain the problem

Local development
It usually is a good idea to create a dummy repository to run your changes.

Expected Behaviour

With this issue I want to purpose a new way for testing melody most recent version against real sample applications.
The idea is basically for us to provide a set of self contained melody applications inside melody repository (like a portfolio), something like:

.
├── samples --- melody top level dir, real applications folder
├────── app1
├────── app2
├── bench
├── bin
├── node_modules
├── packages
├── rfcs
└── testsetup

What we would gain from this?

• A better way to perform e2e testing against melody most recent version making it easy to identify backward compatibility issues that may rise upon new developments.
• An integrated development experience since we wouldn't need to set up a separate repository to link melody and test it, we would have this within the same repository, out of the box (picked from CONTRIBUTING.md Local development section).
• Better documentation. What better to show newcomers how to use melody than a set of different real sample applications with varied complexity?

(NOTE: an example of this concept may be found in the angular/angular repository)