David's changes to work with dbarbar/localdev_install

I can break these out into more pull requests if we decide to not use everything.

1. I got fed up with the Vagrantfile in this repo.  I kept editing the recipes and wondering why my changes weren't going through.  It was because I was editing locally without pushing and Berkshelf was using the remote version.  I think it makes more sense to have the Vagrantfile somewhere else and Berksfile there to pull in this cookbook repo.  So right now I put that in my localdev_install repo but eventually I could see that going in a "get started" type repo.
1. I made changes to the Vagrantfile to move the Chef run list into roles and environments.  I also added support for vmware_fusion and parallels boxes.  I'm running VMWare Fusion.  Parallels will need testing.  We could also change the base box for Virtualbox to match the same as VMWare.  See https://github.com/dbarbar/localdev_install/blob/master/Vagrantfile
1. For some reason the Berksfile isn't recursing as I would've expected.  In my localdev repo I was hoping to only include jrdevsetup but it complained that it couldn't find the other cookbooks.  I thought it would've gotten them from the jrdevsetup Berksfile or metadata.rb.  So my localdev Berksfile ended up having to include all the ones in this repo.  https://github.com/dbarbar/localdev_install/blob/master/Berksfile
1. Updated hosted springboard version.  I don't think it matters when Berkshelf is pulling in a git repo as it always seemed to pull in master.  I could be wrong.
1. Refactored the data bag iteration code based on something I saw somewhere else.  I don't feel strongly about this change either way.
1. I'm using a different base box than the one you picked (https://vagrantcloud.com/chef/centos-6.5) and it doesn't seem to come with the yum-epel repo installed.  That's needed for php53u-mcrypt because it has libmcrypt.  I added that recipe to tools.rb for now, but I guess that should go in jr-php in the mcrypt module recipe?  Does your base box come with yum-epel?