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

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

update to jwcrypto 0.1.1 - now the verifier supports 'new style' assertions which are JWS structures separated by tildes and don't double base64 encode.  assertion size down 33%.  we still generate only old style assertions.  issue #507

issue #632.

* Add a new action - doError.
* Add a new template invalidRequiredEmail
* Add a check in the "start" state to see if the requiredEmail is legit.

close #632

* Now in the requiredEmail flow, the title in forgot password screen remains "The site requested you sign in using"
* Simplified the passing of the forgot_password module parameters.

close #608

Reduce the amount of code - use the generic helper which takes care of the context.

close #765

issue #700 - don't scatter generated files about the tree - create a relative symlink for include.js so we can perform a build somewhere, and then move it about the filesystem

Creating the build and production directories so that we are not polluting our dev directories and overwriting files in the build process.

* Build script creates two new directories, build and production.
* build is for uncompressed files.
* production is for ready to serve up files.
* Set up a symlink for include.js so we do not overwrite the original.
* Update the build script to update include.js symlink.

issue #700

Conflicts:

	resources/static/include.js