Game is "functional" with multiple client connections using Socket.IO

-Game is completely functional and sends question/responses/answer to multiple instances, syncing across all players.
-NOTE: This is just a very rough draft/first iteration.  The following updates/enhancements will need to be made!
--Socket.IO logic needs to be moved into a factory/service and handled separately.
--Data is sent from one instance to another using query strings in the URLs.  This seems kind of hacky, but I could not get it working another way and didn't want to waste too much time for the time being.
--This also made me think that the use of UI-Router is not 100% correct with the multiple controllers, etc.  This can definitely be improved upon dramatically.
--Robot response is hard-coded in right now; need to add in Stef's logic and that whole piece.
--Socket.IO stuff on the server end needs to be separated out into its own file to avoid cluttering the app.js file.
--Would definitely like to review this with someone on the staff/even our code review with Adrian to see if this is the "right" way to do things overall.
--Does NOT include some of the new views we discussed yet (lobby, etc.).  It only starts at the point where the Guesser is asking his/her question.
--Needs tests, duh.

Overall, getting this setup went much more smoothly than expected.  We can walk through this and Collin's OAuth stuff in more detail tomorrow, as these are both big chunks!