Fig

Renamed images to be fig compatible and added a Fig configuration

In fig it is not possible to have settings ( like installation_type=composer|tarball ) in a separate file, so everything is placed inside fig.yml.. Fig does support getting configuration values from environment variables, but I opt'ed not to use that

FYI : Containers will not be named the same by Fig vs Vagrant. ( You cannot fully control the naming when using Fig, only in vagrant )
Ok, [seems](https://blog.docker.com/2014/10/docker-microsoft-partner-distributed-applications/) (mentioned elsewhere before as well but also here if you search for `fig`) fig is planned to be part of Docker, so will be interesting to see in next release if there is some changes around this already.