Fix issues found after deployment

Change the URL on the client settings to the real one.
Instead of the hardcoded one for testing.
Only one this time, this testing business is working!
Check in popup for the visualization view

I don't want to include ionic just to get a popup. Found a CSS-only solution at
http://www.script-tutorials.com/demos/222/index.html#close
which is what I have implemented
Switch the default display to also use ionic

Using something other than iconic with the ionic tab bar causes the tab bar to
be duplicated multiple times (like the "stamp" option in scratch). Fortunately,
we just converted the gamified display to ionic, so this change was easy.

Couple of bonus fixes:
- Removed the message from the HTML because it was taking up too much real
  estate, and the dropdown made it pretty clear anyway
- Added the new blurb on iOS
Add the iOS blurb to the working gamification window

Pretty straightforward change
Merge pull request #31 from shankari/gamification

Convert default view to also use ionic
Scale all the scores down by 10 to make the game more meaningful

Also increase the timeout so that people can actually read the rules
Merge pull request #32 from shankari/gamification

Scale all the scores down by 10 to make the game more meaningful
Add server and result level stats storage

The server stats are automatically stored using the before and after hooks. We
store the uuid and the start time in the request in the before hook, and
compute the duration and store the entry in the after hook.

For the result stats, I just inserted entries at various parts of the code. The
entries are inserted using constants defined in the stats file, so that we know
what all of them are.

I added a new unit test case for the calculation of the sum, and tested that
the stats are inserted correctly manually due to lack of time. A unit test is
pending and will be checked in soon.

All this code is exercised using existing unit tests, all of which pass. The
storage code is copied from the client stats code, which is known to work. For
completeness, we just need to add a new unit test testing that the generated
stats are indeed stored correctly in the database.

I have filed an issue to track this.
Had forgotten to change the name of the method to store client stats

When I created the different stats categories
Merge pull request #34 from shankari/gamification

Add server and result level stats storage
Post-deployment fixes

%&^&$#$#! Should have run the trip manager tests before checking in
Merge pull request #36 from shankari/gamification

Post-deployment fixes