Undo the gradle multi-module refactor

Jason had an awesome idea to refactor us into gradle modules. This made dependency management easier and it also made using IntelliJ much easier since you could open all of Production in a single project window! It was a great change. Unfortunately it surfaced two bugs that we didn't find during normal testing.

The first bug had to do with the POMs being generated in Maven having the wrong ID and version. But that was trivial to fix.

The second bug is in IntelliJ and basically IntelliJ does not handle gradle subprojects in v13 correctly. They had a regression and according to http://youtrack.jetbrains.com/issue/IDEA-120939#comment=27-777233 they don't plan to fix it. I tried their work around but it didn't work. The issue is that when running in IntelliJ the resources directory for modules aren't properly added to the path and so resources aren't found during execution. Since we need those resources that was a show stopper.

IntelliJ says to go to v14 but v14 is an EAP and not even a beta yet (by their own warning language) and anyway uses a newer version of Android that isn't compatible with our version and we don't want to upgrade right now. So we had to lose a good chunk of productivity by the whole team while we pulled out the changes. Sigh.