issue #333.

Conflicts:
	browserid/static/dialog/controllers/authenticate_controller.js

Conflicts:
	browserid/lib/wsapi.js

ensure users must authenticate every week (issue #309).  Also, move all magic numbers out of implementation and into the configuration abstraction.

Potentially use this to create an assertion directly.

Baby steps to getting the stylings looking better.  Trying to reduce the "jumpiness" of elements on the screen.

Now making the "add email" portion show in its own screen so that things look cleaner.

Adding room for 5 email addresses.

Putting all the buttons on the same line to maximize room for email addresses.

Changing the padding/margins of the email addresses so that the glow around the buttons is not cut off.

Thinking that maybe we should remove the email addresses entirely whenenver trying to add a new one.  There is too much clutter on the screen with everything.

Removed some duplicate code.

Made it so you have to change the email input for the password field to go away and a check is reforced on whether the email address is registered.

disable button immediately after click for 'verify email' button, at least the user gets immeidate visual feedback if the stage_user call is slow

  1. indent email addresses
  2. increase whitespace after 'sign in using'
  3. limit height of display so that new email address interaction isn't pushed offscreen
  4. add scrolling to support > 3 email addresses (not pretty, but functional)

remove favicon graphic for now, until we figure out how sites will provide it and write the code to acquire and cache it

We still trying to use the network.origin instead of the local origin.

Moving the registration polling functions out of the controllers into BrowserIDIdentities so that they can be tested and reused.

This completes it!  There are no direct dependencies in the controllers on BrowserIDNetwork.