git-subtree-dir: automation-tests/browserid
git-subtree-split: f4063ba738486918a9a2fedea3545f37f949e3d6

* Remove the signup page and all remnants of it.

Ensure that when a user verifies in a different browser than what they reset their password with, they must authenticate to complete the verification

add access-control-allow-origin to all static resources (excluding views), to allow fonts to be requested cross domain.  fixes a regression introduced during the merge of router, for issue #1973

Allow assertions issued by person to be used to authenticate.  This makes it possible for "proxy idps" to work without the implementation details leaking out into others verifier implementations.

add test coverage of origins that start with digits, and relax validation regex a bit - closes #2042

extensive testing of i18n mechanism - including english fallback, string substition from .json files, and debug locale

perform rigorous validation on all API parameters, cleanup redundancy in sanitize.js and validate.js - issue #1526

Signed-off-by: Lloyd Hilaiel <lloyd@hilaiel.com>

rename the 'add email' email we send out to 'confirm', and use it in both the email addition case, and the email reverification case.  This is more about semantics than behavior change

fix issue GH-1958; add '/production/authenticate_with_primary.js' to items to exclude and reformat the single line array

add tests of email_for_token in the context of password reset, remove old transitional code, fix exception in complete_reset api that was preventing authentication of user.

Add the "verified" bit to emails.
Start shells for the reset_password and confirm pages.

implement complete_reset, stage_reset and refactor database code to support this addition, add tests

The `static` process has been added to handle cachable resources and views, so
code relevant to serving those resources has been removed from `browserid`.

The `router` heartbeat now depends on both `browserid` and `static` processes being ok.
`router` now forwards wsapi writes to `dbwriter`, reads to `browserid`, and errors on unkown
or internal wsapi requests. The wsapi setup for `browserid` no longer handles forwards, though
some wsapi operations may trigger a forward to `dbwriter`.

issue #1793

issue #1794

optimize backend unit tests by starting all daemons in parallel, and then starting router.  issue #1803