Add basic build script

:information_source: - this is (very early) work in progress, as I'm having unexpected difficulties to get `vagrant up` and running properly, thus require a channel to communicate the state of affairs and details of encountered issues.

I've expected my local VirtualBox/Vagrant installation to be the culprit here (be it due to being not current or otherwise defunct) and have updated everything as follows to no avail so far:
* VirtualBox 4.2.12
* Vagrant 1.2.2
* vagrant-vbguest 0.8.0

The latter doesn't work due to the following error:
> You appear to have a version of the VBoxGuestAdditions software
on your system which was installed from a different source or using a
different type of installer.  If you installed it from a package from your
Linux distribution or if it is a default part of the system then we strongly
recommend that you cancel this installation and remove it properly before
installing this version.  If this is simply an older or a damaged
installation you may safely proceed.

I don't think that's necessarily relevant though and have ignored it so far accordingly.

The actual error seems to happen at a random point during isntallation of `ti-debug` and the subsequent `npm` activities, which in turn yield the automatic ssh connection during provisioning to be dropped. That might very well be a Windows only issue due to inferior CLI ssh support, though this build in connection worked fine for me and Vagrant 1.2.x has supposedly improved on this even still (note that it failed for me with 1.1.x and 1.2.x, so it doesn't seem to be related to a regression triggered by the update).

I'll temporary remove the failing automatic provisioning steps now and try to (re)create a working setup from a proper SSH terminal first.