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

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

add unit tests for __heartbeat__, includes exposing PIDs of all running daemons so tests may do stuff with them (like kill SIGSTOP)

fix the fragile static-resource-test - when adding keys to lib/static_resources.js all indexes get shuffled.  broken with addition of relay.js.

Fix start-stop.js test module to look for router output and ignore tokens found in "forwarding request" output lines

added conformance tests.

tests should now pass
updated to jwcrypto that has proper callback delay guarantees and removed unnecessary setTimeouts

Updated all calls to jwcrypto to use the more intuitive API. Fixed a front-end test that was failing due to true asynchronicity of jwcrypto.

unit tests which excercise verification of emails in a "different browser" from whence verification is initiated

require authentication on complete_* wsapis to reduce risk now that password is provided before email verification.  issue #290 and a pre-requisite for issue #1000

remove delay in primary-then-secondary test that was introduced in issue #1445 and is no longer neccesary with the movement of password selection to dialog

* /wsapi/complete_email_addition no longer has to bcrypt the password, so the previously mentioned race condition should be a thing of the past.
* in pages/start.js, signUp is now a module so it has to be started.
* in controllers/actions.js doEmailConfirmed is no longer an action and is no longer needed.

* Update the "stage_user" and "stage_email" to take a password where appropriate.
* Remove pass from calls to "complete_user_creation" and "complete_email_addition"
* Update database drivers to set the account password where appropriate.
* Update unit tests.

re-work complete_email_addition to return faster in the case where a secondary email address is being added - mitigates issue #1445 for the purposes of a hotfix to train-2012.04.11

fix backend unit tests that were failing due to increased input parameter checking on site arguments to stage_user

fixed check for site parameter, it should be an origin not a domain, and fixed all tests accordingly. Was careful not to screw up the verifier tests that are testing for old parameters to the verifier.

(cache unit tests, issue #1353) check for proper X-Frame-Options headers on initial request as well as 304 response

fix fragile static resources tests that verify locale substitution works properly based on the present resource deps and the order which they occur in static_resources.js - broken with the move off jquery

(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.

Adding unit test to demonstrate x-frame-options value for iframed and non-iframed content, after a 304