Editing the `/puphpet.yaml` file should be easier.

[beporter]

As it currently stands, the consuming project defines a /puphpet.yaml file to configure the virtual machine, which is copied into the correct place during puphpet-release package installation through composer. The puphpet.yaml file is committed to the consuming project's repo as the "master" copy of the config to use, since it will be copied into place for anyone else cloning the project and running composer install.

If the user updates the puphpet.yaml file though, those changes are not automatically translated into the VM, which is actually using the puphpet/config.yaml file. This would certainly be easier if our "upstream" (the PuPHPet project itself) allowed us to specify a different config file path, but for now we need to make it easy for the user to get those changes into the right place, even if it's a "simple" cp command. What we want to try to discourage is users making (untracked) changes to their puphpet/config.yaml files directly.

I'm open to suggestions for how to best accomplish these goals.