Move from Google DNS servers to University DNS

The Google nameservers work for just about everybody except production boxes behind a firewall. I'm going to make this change now, but revisit in the future to see if we can make this dynamic on the environment
Add Google nameservers as a backup

Of course, it should do no harm to add additional nameservers for use if the first ones don't come through. This process should still be improved
Watch php.ini and restart php-fpm when it changes

As www.conf is not the only config file..
Move Mysql database and user creation to dbserver state

This is no longer just a development task. Users and databases need to be setup per the pillar data in development and in production.
Use sites and site_args rather than projects

Better naming for production and development
Handle mysql user creation in dbserver before DB and grants

We'll make the user parameters dynamic in the next commit
Use dynamic pillar data for db user, password, and host in mysql.user.present
We're in the dbserver state file, so don't require the dbserver state file
Grant privileges to the correct user with site_args
Move the wp.wsu.edu nginx configuration to a jinja template

This will allow us to use the same configuration for multiple sites on indie.

We'll need a replacement for wsuwp platform shortly
Setup webserver.sls to use a jinja template for site specific nginx config

This will make individual site management much easier and negate the need for project level nginx config files
s/nginx-full/nginx in require.pkg
Don't bring in nginx config from individual sites

Now that we're going with a jinja template for nginx config, this isn't necessary
Pass nginx data from the pillar as context to the nginx jinja template
Add basic server_name and directory to template
Watch all sites-enabled files for changes to initiate a restart of nginx
Require the mysql_user root before issuing other mysql commands
Revert "Require the mysql_user root before issuing other mysql commands"

This reverts commit 3141c38c5438ed4a59f1941d6097467e5cb26e1b.

Right. That didn't work
resolve.conf should be in the main server state file

Nameservers are useful for everyone!

We can make this a jinja template next so that specifying this in dev vs production will be easier.
Load nameserver data from a pillar and populate resolv.conf