Start standing up pydotorg production

This is up and running against the staging database at http://virt-q0dzqq.psf.osuosl.org/. It is not behind the load balancer yet, though this PR would enable the new pool.

Prod elasticsearch is setup on virt-q0dzqq.psf.osuosl.org, but I think there are still integration points in the app for it to be able to it.

Before we go live these are some things that need to happen:

 * Create production postgres credentials - Email sent to support
 * Update the postgres secrets databag with prod credentials
 * Migrate to new DB when it's available
 * Tag the new web node in chef with 'active'
 * Ensure load balancer pool is working as expected
 * Ensure the proper keys and such are in place

Things covered in this PR:

- Note machines allocated for this
- Create a default recipe that determines env from attributes
- Remove staging recipe
- Create prod web role
- Create staging web role
- Create prod elasticsearch role
- Setup load balancer for pydotorg-prod-web
- Inject settings module into gunicorn env (instead of hardcoding in template)
- Add in java recipe as dependency to ensure things are there for yui compressor