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 expect that the reason that this still requires async to be turned off is because of the same issue I mentioned in ```test_ActivePlayers.showActivePlayersPage``` et al.: the click event for ```#game_action_button``` is going out and performing an asynchronous API call (or would be, if we hadn't turned off async), and we're not bothering to wait for the callback to finish before we move on to doing our asserts.