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.

implement 'address_info' wsapi that returns information about an email's current status.  who vouches for it, and if it's a secondary, is the email address known

* Add markup/CSS, including tooltips.
* Add logic to manage_account.js.
* Add changePassword to network/user.js.  Add related tests.
* Update xhr mock so that session_context always returns "valid" info unless contextAjaxError is specified.
* Update the tooltip so that it has a reset function.

close #771
close #114

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