Watch site configurations with watchr and restart nginx when applicable

If a site configuration is edited while Vagrant start_config_monitor is enabled, restart nginx so that the changes can immediately take effect.
Refactor folder naming to better describe intent

nginx config files now appear in an nginx-config directory rather than hanging out in the general server-conf pile. Other scripts are altered to make use of the new location.
Refactor config locations for php5-fpm to a more descriptive spot

Rather than piling up config files in server-conf, group like files for php5-fpm config into a php5-fpm directory.
Move server-conf to a nicer config directory

This feels nicer and it's my party right now. :)
Refactor location of database files and scripts

Because databases aren't necessarily configs.
Catch up the Vagrantfile with some directory changes

We were pointing to server-conf still even though the directory had been moved to config a while ago.
Better describe (inline) the purpose of the bash_aliases file
Refreshed gitignore to match new file locations
Now that the database directory has been move, it needs to be explicitly mapped
Import script was looking at a hybrid of old/new locations.
Refer to the proper location for the watchr script in bash_aliases
Update the watchr script to monitor for php5-fpm config changes and restart the service accordingly