reduce qunit failures on jenkins

* Fixes #1104 (i claim)
* Increases qunit test timeout from 60s to 180s (this was already done by hand on jenkins, updating puppet to match)
* Upgrades qunit to 1.15.0
* Change test syntax to take advantage of qunit-1.15.0:
  * Use per-test "assert" objects throughout
  * Use `test() { stop();` instead of `asyncTest() {` for clarity
  * Reduce use of `ajaxSetup` as a workaround to control test synchronicity

Jenkins: http://jenkins.buttonweavers.com:8080/job/buttonmen-cgolubi1/337/
I think this is another one that's the same situation as ```test_ActivePlayers.showActivePlayersPage```. However, in retrospect, something occurs to me: the only thing that these tests (the ones similar to ```test_ActivePlayers.showActivePlayersPage```) are testing for is the existing of the #blah_page element. That element is added snychronously. So technically, everything we're testing for is synchronous... but most of the stuff the function does that matters is part of an asynchronous call that A) we're not testing at all and B) continues to go off and do its thing in the background while we've presumably already moved on to another test. I am not sure how to feel about this, but maybe it's not something that this pull request should need to care about. (On the other hand, having asynchronous calls going off and doing stuff while we're running different tests might be *exactly* the sort of thing this pull request should be caring about?)