makebuildserver: bootstrap directly rather than box packaging
@relan noted that the vagrant package step in makebuildserver
takes up a lot of time and space. There are not many benefits to this, since the resulting box has a rather unwieldy size.
We're using the box for propagating the buildserver base image from the location where provisioning happens (.../fdroidserver/buildserver) to the location where it's used to build apps. (.../fdroiddata/builder). Boxes are the only way of propagating vagrant VMs I'm aware of. Boxes also serve as a clean way to bootstrap a VM into a defined state.
To achieve this we'd need to change the behavior of makebuildserver
to directly create .../builder and provision it right in place where it's created. We'd also have to strip all parts from build.py
which deal with bootstrapping ./builder and replace them with a check, whether builder is present and ready to use.