Unify minion configuration between dev and prod

Our basic requirements in the minion config should be the same. Pillar data can be stored privately on each minion for use during provisioning. This is where differences between production and development should appear.
Match the host ID for wsuwp-indie-dev rather than the environment
Remove the unneeded environment grain
wsuwp-indie-dev states should match on the minion ID, not the grain

This allows us to use the same minion configuration for production and development. State files are processed based on ID
Remove custom grains on wsuwp-indie-dev

We aren't really using these right now, so we should rethink the purpose of having grains in the minion configuration first before attempting to use them.
Add some documentation to the wsuwp-indie minion configuration
Load the devserver states for wsuwp-indie-dev
Remove the vagrant user.present state

I don't think we need this at all. Definitely not useful in production.
Start checking for pillar data again in wsuwp-indie-dev
Grab MySQL password from the minion's pillar data

As of https://github.com/saltstack/salt/pull/9722, this should allow for a password to be set and used properly throughout provisioning.
Add default MySQL data back to minion configuration

This is required for thing to work properly
Move mysql user and pass config solely to the minion's pillar
Use explicit priviliges when granting in MySQL

I'm getting an error with Salt when ALL PRIVILIGES is used. Attempting to take this approach instead.
Use explicit priviliges on wsuwp-indie-dev too

The last commit only affected wsuwp
Merge pull request #34 from washingtonstateuniversity/prod-fix

[PR] Adjustments to WSUWP Indie provisioning