(loadgen) fix subtle issue whereby a XXX@loadgen.domain users's password could be changed during load generation, and affect subsequent runs.  closes #681

(loadgen) fix bug in reauth activity.  in addition to clearing cookies, we must clear client state to cause re-authentication to occur.  maybe the cause for issue #682

close #685

close #690

IE8 does not support delete localStorage.[itemname], so this has to be changed to localStorage.removeItem(itemname)

close #688

* Reducing the number of setTimeouts used.
* Using completion callbacks instead.
* Adding a cancelEvent to the helpers which is a decorator around DOM handlers to cancel the event.

close #686

close #685

update to latest jschannel - closes #534 (innocuous console errors when messages are posted to the frame where include.js is loaded that do not have valid JSON as a payload)

run mysql tests *first* (they're more important), and if we can connect to db but browserid table doesn't exist, we still have db connectivity and can run tests

remove process.exit() from loadgen upon email addition failure.  loadgen shouldn't stop till it reaches the top.

disable http agent in http_forward - it has been capping us at five simul forwarded requests per backend process (dbwriter, keysigner)

(loadgen) optimization - re-use assertions to generate synthetic load without the client compute cost

fix regression in keysigner - ensure non-default VAR_PATH is relayed to compute processes - issue #213

tiny optimization to test running.  don't have the script that checks for db connectivity create any tables

remove the deep __heartbeat__ checks performed from browserid (the webhead), while dbwriter should ping the database to ensure health - closes #566