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

Change browserid.org urls to persona.org, introduce static.login.persona.org for all static resources.

update the http_forward module to allow global request timeouts to be set, use this to implement a 15s upper bound on requests for declaration of support in development.  This should fix unit tests

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.

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

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

Adding disable_locale_check flag to skipping warnings for en-US without gettext files. Fixes Issue#1055

add Vary headers to help downstream caching proxies optimize caching of static resources - closes #938

always run our little node HTTP proxy locally to constantly test HTTP proxy support which we'll have in production - issue #904

Adding i18n to wsapi. Split strings into client.po and messages.po.

Switched email from mustache to EJS templates.

Created fake locale db-LB for development and debugging.

Updated scripts.
See http://viewvc.svn.mozilla.org/vc?view=revision&revision=99911

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