vagrant: Fix regression in provisioning path
vagrant: Fix regression in provisioning path

When I switched to sshfs, I also changed the sync path to `..`,
because sshfs (by its nature) syncs symlinks, rather than following
them, and some of the roles point to the toplevel.

However, things sort of appeared to work, except we subtly stopped
using the `ansible.cfg` file.  Fix this by changing the provisioning
paths.

cwilkers/openshift-ansible-contrib,scollier/openshift-ansible-contrib,cwilkers/openshift-ansible-contrib,scollier/openshift-ansible-contrib,pschiffe/openshift-ansible-contrib,openshift/openshift-ansible-contrib,detiber/openshift-ansible-contrib,dav1x/openshift-ansible-contrib,openshift/openshift-ansible-contrib,cooktheryan/openshift-ansible-contrib,glennswest/openshift-ansible-contrib,openshift/openshift-ansible-contrib,cooktheryan/openshift-ansible-contrib,Tlacenka/openshift-ansible-contrib,Tlacenka/openshift-ansible-contrib,detiber/openshift-ansible-contrib,scollier/openshift-ansible-contrib,pschiffe/openshift-ansible-contrib,pschiffe/openshift-ansible-contrib,detiber/openshift-ansible-contrib,dav1x/openshift-ansible-contrib,dav1x/openshift-ansible-contrib,scollier/openshift-ansible-contrib,detiber/openshift-ansible-contrib,cwilkers/openshift-ansible-contrib,pschiffe/openshift-ansible-contrib,cooktheryan/openshift-ansible-contrib,cwilkers/openshift-ansible-contrib,dav1x/openshift-ansible-contrib,Tlacenka/openshift-ansible-contrib,Tlacenka/openshift-ansible-contrib,cooktheryan/openshift-ansible-contrib,openshift/openshift-ansible-contrib