feat(client): Forward the `resume` token to the auth server

feat(client): Seamless verification in a second browser.

* Create a `resume` token from OAuth parameters. Pass it along to the fxa-js-client.
* Re-populate OAuth parameters from resume token on email verification.
* Bump fxa-js-client to 0.1.25 with the new `resume` hotness.

Remaining work:
* [x] - Merge #1665.
* [x] - Add some functional tests
* [x] - Check for missing parameters from the resume token. Allow user to finish verification, just do not allow redirect.
* [ ] - Check to make sure the serviceName is not displayed if the user is verifying in a second browser but they cannot redirect. Can this happen?
* [x] - ditch the `oauth.client_id` standardization for now.
* [x] - ditch the cleanup when importing uid/code
* [ ] - See if there is a way to introduce a broker to answer whether the user can resume the flow in a different browser?
* [x] - rename canResume to canResumeInDifferentBrowser or something more meaningful.
* [x] - `email` does not belong on the Relier, possibly time for a shell of a `User` module?
* [ ] - Merge updates to 123done to allow verification in a second browser. See https://github.com/mozilla/123done/pull/121
* [ ] - Add functional tests to ensure that users without a `resume` token or with a malformed `resume` token can still continue.

issue #1623
This needs to be brought back for users who cannot complete the oauth flow because of a missing/malformed resume token.