COD without Organic Groups

For the time being, because of the many changes being implemented in this branch, I think it's a good idea to make this pull request to the cod_sans_og branch and not the master branch. The cod_sans_og banch already exists in the upstream and it already contains the bulk of the changes. This pull request is really an alert to the team to fetch the upstream and test things out.

Additional steps to take to test COD without Organic Groups (branch cod_sans_og)

1. Back up your local database.
2. Fetch upstream. 
3. Switch to cod_sans_og branch
4. Go to admin/config/group/fields
5. Delete all OG fields.
6. Change status of cod_base, cod_events, cod_session, and cod_sponsors from 1 to 0 in the system table of your database. 
6a. TODO: I'm writing an update hook this status change and I will update this pr shortly. Because there is urgency around the issue, I thought surfacing to the team what I have ready takes precedence. The modules, cod_base_sans_og, cod_events_sans_og, cod_session_sans_og, and cod_sponsors_sans_og will work just fine even if the database "thinks" their progenitor modules are still enabled (status = 1).
7. Disable OG modules. Don't uninstall them.
I think we should disable the OG modules at this time because when OG is installed it is too embedded in Drupal (think of Fields, Views, and Rules). With the OG modules disabled, the admin does not offer OG options and this will hopefully negate confusion.

You can also review COD without Organic groups at http://cod_sans_og-nyccamp2014.gotpantheon.com/