A lot of cleanup to make the site smoother, IE8 fixes, removing dead code, make the arrow transition smoother.

* On the main page, update card with new design.
* Simplify a lot of styles and layout.
* Clean up the "about page"
* Using css transitions for the arrow slide.
* Change all BrowserID text to Persona.
* Fix a problem on the main site where the footer would was not at the bottom in Webkit and Opera browsers.
* Fix the background color or IE8 in the signUpForm and congrats messages.
* When signing in to the main site, use a tooltip instead of error message on incorrect password.

* A lot of bulk changes to both the main site and dialog.  Updated color schemes, background colors, etc.

issue #1635

* Add the startExternalDependencies option when initializing the dialog controller, if set to false, no external dependencies are loaded.  Used for testing.
* Add a new test to check for script containing emails.
* Add unit tests for tosURL and privacyURL.
* Add a testHelpers.testErrorNotVisible
* Removed the actions.js->doError and its tests, it is no longer used.

Instead of showing an error message, show a tooltip when the user types a bad password in the add_email_address and verify_email_address screens.

issue #1557

* Removed the .interactionData namespace from storage.js, created our first model - shared/models/interaction_data.js
* Simplified how data is stored into interaction_data, created current and staged sub-namespaces
* Added stageCurrent and publishStaged functions.
* in shared/modules/interaction_data.js, simplified calls to model.
* Tried to make the xhr mock make more sense and provide facilities usable for peeking at last XHR request data.

issue #1597

Make users who have not yet set their password by time they reach the landing page set their password.

issue #1592

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.

* user.js: Update verifyEmail and verifyUser to take a password.
* network.js: Update completeEmailRegistration and completeUserRegistration to take a password.
* Replace verify_email_address.js and add_email_address.js with a single verify_secondary_address.js to reduce duplication.
* Update the templates.
* Bring back verify_email_address and add_email_address templates, but remove the verify password field.
* To dom-jquery, add show, hide functions.

* Move #thisIsNotMe button handler from the page_module to pick_email.
* Remove extra tests for the authenticate controller.
* use the alias for BrowserID.User in helpers.js
* Add password fields to the forgot page.

* Verify the user without checking for passwords on the verification pages.
* Update /wsapi/stage_email to take a password.
* Remove the password fields of the verify page forms.
* Set the password when adding an email address.

* Remove the forgot_password controller, templates, tests, etc.
* Update authenticate to trigger "new_user" with rehydration info
* Update set_password to be able to handle resetting passwords as well.
* Update the state machine to handle password setting or resetting.

* This fixes a problem where it is possible that a user takes more than 2 minutes to answer, making the already generated assertion invalid.
* A lot of general cleanup of the state machine.
* Push all post email selection flows to a new state, "email_valid_and_ready" which decides whether to ask the user the computer ownership status.
* Assertions are generated after the "is this your computer" is asked.
* doEmailChosen is replaced with doGenerateAssertion - there were multiple calls to generate an assertion, not very DRY.
* Fix a problem in network.js where a user who completes user registration should be marked as authenticated.
* rename email_chosen.js to generate_assertion.js to clarify its purpose.

issue #1460

issue #1461

* Secondary links all are some shade of dark grey/black with a dotted underline.
* Change the font used on the "about" page to be the standard Helvetica Neue except for the header.
* Change the style of link in the TOS/PP to black text with a dotted underline.
* Loads more link updates!
* A lot of cleanup to remove duplicate `color: #549fdc` entries by using the action class.
* On the main site, put the action links to the far left of the main button.
* Reduce the amount of "forgot password" CSS by generalizing.
* Generalize the yellow banner on the main site.

issue #702

A bunch of changes to make the design more responsive to all screen sizes - mobile, desktop and tablet.

* Start with a slight refactor of the CSS and DOM.
* Vertical center content when content is smaller than the screen size.
* Constrain email addresses and show ellipsis if emails overflow box width.  Make sure width is updated when browser window size changes or user changes the screen direction of their device.
* If form/email address list is taller than available form area, show scroll bar on desktop or expand contents so that entire app must be scrolled on mobile.
* If dialog opened on a tablet or large desktop window, add a gradient to the left size of the white area that matches the gradient on the arrow.
* On mobile, footer should always be at the very bottom of the screen unless contents overflow screen height, where it will be pushed off the bottom of the screen.

Things to test and be aware of:
* Dialog should respond to various screen sizes when resizing browser window on desktop.
* IE8 does not support media queries so narrowing the browser window will not force the dialog into "mobile" mode.
* Contents in the "form area", wait, delay, or error screens should always be vertically centered.
* IE6/IE7 should still see the unsupported dialog with the correct layout (untested on checkin due to #1390)
* Wide emails should always be constrained to the screen width on mobile or box width on desktop.  The layout should respond to changes in device orientation.
* The box surrounding the emails should show a scroll bar on desktop/tablet if there are more emails the available screen height.  On mobile, the entire screen height should expand so that the entire app must be scrolled.
* On mobile, the footer should always be at the very bottom of the screen unless the form area takes up more vertical space than the device height.

issue #1101
issue #1317

issue #1397

* Show a tooltip if the passwords are the same.
* Clear old and new passwords if the password is successfully changed.

issue #1388
issue #1389

* Start with generic Firefox and iOS

issue #1167
issue #1302

* Add a unit test harness for is_this_your_computer
* When the user authenticates, set them as seen.
* In storage.js, Use an object to store the usersComputer info instead of arrays for developer grok.
* Add storage.js->clearUsersComputerOwnershipStatus for testing.
* Clean up user.js->logout a little bit.
* Completely clear localStorage between every test.
* Add tests to check for when the user should see the "is this your computer" screen.

partial implementation of issue #1196 - add a 'logout of all websites' button on manage page, and implement monitoring of change of login state via polling (IE8) or storage events (everyone else at the party) - fire logout events when the user logs out.

* Change the layout so that the entire form area gets the scroll bar for languages that use a lot of text or if the user has a lot of email addresses.
* Change the way the privacy policy and buttons are rendered so JS is not needed to set the width of the privacy policy.
* Put the TOS on its own line.
* Put "Always sign in using this email" on its own line
* Change the order of the "Forgot your password?" button and "password" label so that Germanic languages render the entire thing on one line.
* Remove the "Sign in using" header text.

issue #1300
issue #1286
issue #1275
issue #1274
issue #1272
issue #1262
issue #1261

issue #1189

Using @fawek's pull request as a base for a full solution.

* If the user clicks on the label, proxy the click event to the input element.
* If the user clicks on the input element, let the browser handle things.
* Add user tests to check clicks on both labels and input elements.

issue #1155

Instead, translators will see a %s and the href and target attributes will be added dynamically.

issue #1160

The problem stemmed from the DOM was not completely reset between every test.  When the manage page inserted email addresses into its portion of the DOM, it added email addresses with elements with the same ID as the pick email controller.  Instead of ensuring we clean wipe these elements between every test, rely on QUnit's ability to reset a portion of the DOM to its initial state.

* Add the `qunit-fixture` class to the bit of DOM that should be reset between every test run.
* Add the testHelpers.setup/testHelpers.teardown functions to several suites that manually called emtpy() on DOM elements.

issue #1156

* Use format to insert the URL.

issue #835

issue #1113