feat(client): Add support for `preVerifyToken`.

`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server
then does a dance with the trusted RP to determine whether to create an account for the user without
the need to verify their email address. If the user is pre-verified, the signup flow completes at the
`/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their
email address as is currently done.

This PR also introduces the concept of a `Relier` model. A Relier is a model
that represents an RP and information about/from the RP.

issue #1540

Items that still need to be completed:
* [x] - Update the fxa-js-client to pass along `preVerifyToken` - See https://github.com/mozilla/fxa-js-client/pull/127
* [x] - Update the fxa-auth-server to handle `preVerifyToken` - See https://github.com/mozilla/fxa-auth-server/issues/780
I think the "pre-verified" should behave just the login flow, which for the OAuth flow means that you just drive the OAuth flow to completion. I can see maybe you're trying to be DRY with https://github.com/mozilla/fxa-content-server/pull/1606/files#diff-c48d7c0a638b28615a3a24a78745c085R43, but I'm not sure the current strategy works. We could just take them to `signup_complete`, but it seems unnecessary.