Missed adding new dbutils.js
unverified email

An implementation for B2G to ask allow users to log in even if
Persona has not verified that the user owns the email address.

Starts with navigator.id.request({ allowUnverified: true });
When the assertion is returned to the RP, and if they are using
the Persona verifier, must be sure to include an allowUnverified=true
parameter to the verifier, otherwise it will be rejected.

Behind the scenes, when the dialog tries to stage the user, instead
the user is created immediately, an email is added in our email table,
and a stagedEmail token is created and send to the user. When
allowUnverified is true, our wsapi will also check for a staged email/pass,
and use that to allow the user to login.
add gradients back in
unverified email now adds passwd to user row

this makes things a whole lot simpler underneath
fixing cef_logger.alert, and INSERT INTO user
I think a recent merge removed these forceIssuer pieces
Merge branch 'b2g' of github.com:mozilla/browserid into b2g
email inserted in mysql should be `unverified`
Bug 823736 - objects must be stringified between gecko and user js
The verifier service should be explicit about unverified email in it's output
Merge pull request #2898 from ozten/explict-unverified-verifier-output

[b2g] The verifier service should be explicit about unverified email
authenticate with unverified email and allowUnverified

fixes #2902
Merge pull request #2907 from seanmonstar/2902-reuse-unverified-email

authenticate with unverified email and allowUnverified
Bug 827558 - rename native navigator.id to .mozId