Use Vagrant to initalize and provision a consistent development environment

[alexcabrera]

Instead of having to worry about which versions of npm, compass, sass, and the various Python and Node.js requirements, we can just use Vagrant to provide a consistent environment for development and (possibly) in production.

The Getting Started section in the README.md updates of this pull request provide instructions on how to work on the runtime under Vagrant, but basically require you to do the following:

1. Uninstall binrary release of Vagrant and build from source
2. Install Ansible from source with Homebrew
3. Add the following to your ~/.ssh/config;

    Host 10.10.10.2
      StrictHostKeyChecking no
      UserKnownHostsFile /dev/null

1. vagrant up
2. vagrant ssh

When you ssh into the box, the .profile file that's copied over will activate the runtime virtualenv and put you in the right directory (/home/vagrant/runtime).

Until we move to a non-Flask specific command line interface (merging the feature/docopts branch would be a good start), you'll need to manually set the host when running the debug server by issuing the following command:

(runtime)[/home/vagrant/runtime]$ python manage.py runserver -t 10.10.10.2

[alexcabrera]

Ok, I think this is good to go now. Ansible provisions without error, added a runserver alias serves up the runtime at 10.10.10.2:5000.