Fix inconsistent state assignment

[luisrudge]

The correct way of sending the state parameter in the authentication request is

var options = {
  auth: {
    params: { state: 'foobar' }
  }
}

But, because of the bug I just fixed, this state, although being sent in the auth requests, wasn't being sent in the parseHash method, which caused the 'state doesn't match' error.
This gets the correct state without breaking anyone.

With this code, both version will work for parsing the hash with a specific state:

var options = {
  auth: {
    params: { state: 'foobar' }
  }
}

var options = {
  auth: {
    state: 'foobar'
  }
}

[lbalmaceda]

Documentation should be clear over which state param is ultimately used. In the case of setting it on both places, the opts.params.state ends up being the one used.

[joshcanhelp]

@luisrudge - if they have both then the former example in your description will override the latter. Is that expected? Is it consistently documented one way or the other?

[joshcanhelp]

Discussed the overriding and looks good as-is 👍