Hook up the new FxA JS client.

* Update bower config to fetch the new FxA JS client.
* In postinstall npm command, install the FxA JS client's dependencies and do a build so the client is available.
* Create a light wrapper around the FxaJSClient to reduce boilerplate code.
* Use the fxa-js-client from the bower install, get rid of picl-gherkin
Updates with @zaach's suggestions.

* Rename gherkin to fxaClient
* Use the special xmlhttprequest that supports .onerror
* Rename the FxaClient wrapper to FxaClientWrapper internally
Merge pull request #204 from mozilla/issue-203-new-js-client

Hook up the new FxA JS client.
Start the complete_sign_up screen.

* Fetch the code, uid, and service from the URL search string.
* Handle errors
* In the create_account screen, only attempt to create an account if both email and password are available.
* rename tests/functional/signIn.js => sign_in.js and signUp.js => sign_up.js for consistency.
Merge pull request #195 from mozilla/issue-194-email-verification-screens

email confirmation flow.
Add Mike Trinkala to authorized_keys on the awsbox.
Merge pull request #209 from mozilla/rfk/add-trink-ssh-key

Add Mike Trinkala to authorized_keys on the awsbox.

r+.

@rfk - does it make sense to add this pubkey to [identity/pubkeys](https://github.com/mozilla/identity-pubkeys) too?
Add the fx-desktop channel & start to set up front end unit tests.

* Add mocha & chai to the bower config.
* Add a functional test shell for the confirm screen.
* Go to the correct page on startup if the browser supports Fx events.
* Mocha tests now run as part of the intern functional tests.