[ADD] introduce copier to initialize and update projects

[thomaspaulb]

I wanted to use the waft repository for the template project at first, but I saw that it was also possible to use a subfolder of the main repository. It works just as well, so in that case maybe we can drop the waft repository, we wouldn't need it anymore.

[thomaspaulb]

@Hussam-Suleiman This is a very minimal change to Waft. It introduces copier, but only for the initialization of a new Waft project (which Therp employees don't often do, only perhaps the "new BoC" ansible calls this and would have to be changed)

Another change is that the cloned project does not have a Git repository by default; so if pushing it somewhere, then first a Git repository will need to be created with git init or so.

And another change then would be that people should not rerun bootstrap but rather run copier update if they want to update their project.

What I didn't do yet but should probably do is think of some way to convert the current projects to copier projects. They were not started in that way. Basically the waftlib and odoo versions will need to be taken from the existing files that are there, and then copier update will need to be run, with the default answers filled in.

There is much more that can be done with copier, with versioning and pre/post migration scripts that are run on copier update from the source; and also to replace symlinks with actual copies, that are then always compared to the source upon an update. But that I would like to try after this is accepted.

[thomaspaulb]

Moved to sunflowerit/waft#7