feature(client): Pre-fill password on /signin when coming from /signup if user entered an existing account.

Other items:

* Add more unit tests to signin and signup
* Whenever focusing an element, place the cursor at the end of the text.
feature(client): Prefill form fields if a user changes from `/signin` to `/signup`.

* If both the email and password are filled out, autofocus the year.
* /signup form fields are pre-filled if user clicks on any /signup link from /signin
feature(client): Prefill email address on /reset_password for users who come from /signin

issue #1047
fix(client): Prefill the user's email on /signin if the user clicks the "sign in" link from "/confirm_reset_password"

fixes #1038
fix(client): Fix email field focus in Chrome. No more exceptions.

* Chrome has a bug where setting the selectionStart or selectionEnd of an input[type=email] element throws an exception. See https://code.google.com/p/chromium/issues/detail?id=369499
cleanup(client): Rename focus* variable names to shouldFocus* in sign_up.js for clarity.
cleanup(client): Standardize on `AuthErrors`. Convert all `authErrors`.
chore(l10n): change email marketing string
If the user enters an unknown email address in `/reset_password`, give them the option to go to `/signup` and pre-fill the email address.

fixes #1046
Merge pull request #1093 from mozilla/issue-1042-email-marketing-strings-2

chore(l10n): change email marketing string
Merge pull request #1048 from mozilla/issue-1047-prefill-everywhere

form prefill everywhere
test(functional): use Intern config to specify server
Merge pull request #1068 from vladikoff/lcip-tests

test(functional): use Intern config
feature(build): Pre-build static pages and CSS for each locale.

Use grunt-connect-fonts to generate locale-specific CSS and extract font files. A copy of the all static pages are generated for each locale. This allows grunt to pre-generate locale specific CSS files which are included into the final page. This concept can be extended to do two things:

1) Pre-translate all static pages
2) Create JS files which contain the client side translations to avoid the extra request for client.json

Additional build steps and a new middleware are needed to make this happen.

1) grunt: We have to create @font-face CSS declarations for each locale. The @font-face declarations contain links to the correct font for that locale.
2) grunt: We create copies of each of the static pages in server/templates/pages/src into server/templates/pages/dist/<locale>
3) grunt: requirejs must replace require.js script with production version for each page from 2
4) grunt: usemin must replace dev CSS with the appropriate localized production CSS.
5) middleware: A new middlware, /lib/localized-render.js, is added that renders the appropriate template for the locale when using dist content.

fixes #860