(test fix) when checking that certificate duration is correct based on 'ephemeral' argument to cert_key api, allow a 200ms window to account for a small elapsed time between setting of iat and exp - which occurs on a system under load or slower virtualized environments (like travisci)

API changes for public terminals/shared computers, and update all tests
to post data using JSON rather than form encoding, as the front end now does.

implement and test the prolong_session wsapi - which extends the duration of an existing session from the ephemeral duration (an hour) to full authentication session length (2 weeks) - doesn not change the start time of the session, so is a noop when invoked multiple times.  to be added to frontend code once user acknoledges ownership of device.

update cache header tests because etagify lazy calculates content hashes for etag headers, see comment in commit contents

Cachify CSS while compressing it. Fixes Issue 620

Add the groundwork for browser specific "Enable Cookies" URLs.

* Start with generic Firefox and iOS

issue #1167
issue #1302

Reusing staticPath in compress worker and making prefix configurable, removing DRY violation per llyod

Fix cookiesEnabled being possible to call it's onComplete callback twice if onComplete throws an exception the first time.  closes #1339 - related to issue #1323

Fix cookiesEnabled being possible to call it's onComplete callback twice if onComplete throws an exception the first time.

issue #1339

use etagify for content-based hashes in ETag headers - issue #1331

when a user has not confirmed a device as their own, and they are autheticating with a primary email address, convey to the primary that a shorter cert duration should be used

update cache header tests because etagify lazy calculates content hashes for etag headers, see comment in commit contents

add a ping wsapi that's registered on all daemons and does a light weight test of database health - closes #1324

* Adding a "setUserMustConfirmComputer" function to storage. This forces the user to confirm whether the computer is theirs.  Used for testing.

* Fix the tests that had to do with the assertion_generated.
* Update the XHR mock to pass back the userid on authentication.
* Do the closing animation just before the dialog is actually ready to close.

ask a question in a code comment about the implementation of getSilentAssertion which we now use in the comm iframe for the event api implementation

fix bug where when authentication state is changed in-dialog the comm iframe wouldn't notice, and would conclude the user is not authenticated based on a cached session_context response

* state.js - rename "publish" to "redirectToState", rename "gotoState" to "startAction" and "subscribe" to "handleState" for clarity.
* state.js - do the "is this your computer" check from "assertion_generated" so that it is taken care of for all types of assertions (primary, secondary, required).

* Add a unit test harness for is_this_your_computer
* When the user authenticates, set them as seen.
* In storage.js, Use an object to store the usersComputer info instead of arrays for developer grok.
* Add storage.js->clearUsersComputerOwnershipStatus for testing.
* Clean up user.js->logout a little bit.
* Completely clear localStorage between every test.
* Add tests to check for when the user should see the "is this your computer" screen.

enforce that deprecated APIs aren't combined with new apis.  optimize away comm iframe when deprecated APIs are in use.  emit a message to the console when deprecated apis are in use