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

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

(aws deploy) another bug in deployer support for multiple keys - call copyNext() to start key copying

rework how we decide when to ask about computer ownership: no is sticky for 24 hours.  only ask if it's been 1 minute since we first saw the user (not on the first login).  also defend against garbage in localstorage.

fix bug where we wouldn't know the userid immediately after authentication.  return userid from authenticate_user api and set it upon successful auth.

* Adding checks for all expected navigator.id based functions.
* pick_email.js - Get rid of the "remember" tests
* state.js - Check that authenticated redirects off to "email_chosen"
* user.js - get rid of the setPersistentSignin, change removePersistentSignin to logout.
* xhr.js - Look in the stringified JSON for the csrf token.

fix unit tests - autenticate_user and cert_key now require a boolean 'ephemeral' value which will affect duration of authentication and certificate validity respectively.

fix transition after answering the 'is this your computer' question - automatically complete signin after answering

when certifying secondary certs and the user has not confirmed their ownership of the given computer, certify with a short validity period

wire up buttons of 'is this your computer' - functional but needs work (an extra click, figuring out all the places to ask the question, etc)

use a 'wait' screen for the is this your computer question, needs styling and yes and no buttons to do the right thing