(loadgen) tons of fixes to handle request failures without mucking up the local user database - issue #838, issue #785, issue #787, issue #784

when loadgen emits errors, indicate what activity was being performed when the error was encountered.

implement a 'maximum request time' for bcrypt work.  server now fails more gracefully under backbreaking load, returning 503s to clients of the authenticate_user api.  update loadgen to be less dramatic about, but still display, 503 errors.  first part of issue #787 - a partial fix for #785 in dere too

(loadgen) fix console output at startup - properly message # of pre-created users or users to be created via API

(loadgen) add '-l' option to list activites, and '-a' option to specify a list of activites to run (ignoring others).  simplify '-o' so all this stuff uses the same mechanism

(loadgen) add -u option that allows one to specify a numeric range which will make load testing with a large database possible - issue #504

(loadgen) implement assertion generation in loadgen client, hook up signup and signin flows - issue #504

(loadgen) now starts up, generates 30 keypairs, adds 30 users - simulated signup mostly updated to new apis - issue #504

repairing load_gen - issue #504 - update pathing, alter fake_verification WSAPI to query the database rather than to use email interception (which no longer works)

upgrade to bcrypt 0.2.4 and move to bcrypt async apis, this keeps us from blocking the web server thread and leverages the threading support in the bcrypt library for better compute throughput and responsiveness.

output human readable summary information of what kind of load will be applied when the load gen starts with a fixed target number of active users.

(load generation tool) implement the 'include only' activity, which simulates an RP including include.js

(load generation tool) complete main run harness, including regulation of the number and type of activities to run, and the output of current active users being simulated

initial implementation of structure of load generator, including encoding probabalistic launching of activities

find instances of console.log() and send them to the logger instead, when running under dev harness also route to console.  issue #169

simplify verifier a bit to make it simpler to use either off the same domain as browserid.org OR on its own domain.

in source urls are now all (interim == eyedee.me) live, the test harness subs in testing urls & hostnames

a little wrapper file to run the implementation provider/secondary thingy standalone outside of the test harness