move 'primary.js' - abstraction for interacting with primaries - down to lib/, now it's used by different processes

WSAPI CHANGES: implement auth_with_assertion wsapi.  this requires creation of a new create_account_with_assertion api on the dbwriter than cannot be externally invoked (though it still re-verifies assertions).  New mechanism added to wsapi.js to support this type of function (internal only wsapis)

implement support for verifying assertions issued by primaries for the purpose of logging into browserid

SCHEMA CHANGE: password is now nullable in schema.  also, add .createUserWithPrimaryEmail and .emailType to db abstractoin

when running locally, SHIMMED_PRIMARIES set for all daemons (so dbwriter can interact with primaries too)

* Adding a window Mock.
* Adding a new template for the "you've gotta verify" screen.
* Hooking up the logic to redirect - which closes the window.

* Add network.authenticateWithAssertion and related tests.
* On signup page, start the redirection code to verify with primary in new tab.
* in network.js, rename all the onSuccess to onComplete for clarity.
* Simplify tests for primary user provisioning while "not authenticated".
* Generate fake keys/certs in the provisioning mock.
* Save off the keypair/cert given to us by the provisioning frame before getting an assertion.
* Generate an assertion and log the user in on primary provisioning success.

API CHANGES: stub a new auth_with_assertion api for authenticating to browserid with assertions generated from primary issued certs, and implement a failing unit test.  now lets make it pass

SCHEMA CHANGE: add a bit to the email table describing whether emails are primary or secondary, update list_emails wsapi to return this, augment unit tests

use crypto.getRandom instead of urandom closes #735

changed generate to use nodejs crypto, added weakgenerate, added async support for generate, and added tests

attempt #2 at resolving duplicate ids, rename the new one that's used in fewer places.  fixes frontend unit tests

This reverts commit 3e88cc39.

revived the navigator.id.channel, as well as the #NATIVE and #INTERNAL indications that internal APIs are about to be called

Conflicts:
	resources/static/pages/signup.js
	resources/static/shared/network.js

* Adding unit tests for network.addressInfo
* to the XHR mock, adding info needed to test primary/secondary flow.
* Adding a BrowserID.Mock.Provisioning to handle mocking out provisioning capabilities.
* Creating a new User.createUser that handles creating users on either primaryies or secondaries.
* Adding unit tests for the signup page for primary, updating old tests for secondary.
* Starting a shell of error messages and success markup on signup page.
* Starting to hook up the dialog, adding loads of tests.  Secondary based user creation good again.

implement a more generic mechanism to enable local testing and development of primary support - allow SHIMMED_PRIMARIES to be provided which stuffs a auth url, provisioning url, and public key in our cache

implement both sides of the 'provisioning_api' - that which primaries interact with while certifying authenticated users. woo.

partial implementation of trusted side of provisioning setup, enough to try to load primary's provisioning url

plumb primary check into signup page on main site, partially implemented, but enough to develop primary provisioning page with

stub in a new javascript library that will abstract dialog code from the details of embedding and interacting with a primary's provisioning content.