Updated: jwt-go is now v3.0.0.

[leetal]

This PR is in direct response to #76.

NOTE:
No direct breaking API changes should have been introduced in this pull request, as long as no one explicitly uses the raw values of "iat", "exp" and "nbf" claims (was int, is now float). This is due to the fact that jwt-go needs float64 types when validating the claims. I will create a new PR to jwt-go as well that is going to allow int64 values to be parsed. Hopefully it will get merged fast. If that's the case, after a minor upgrade to fosite removing the float64 casts, nothing API-wise will have changed since before the upgrade to jwt-go 3.0.0.

// Alex

[leetal]

I have supplied a PR to jwt-go now that will fix the "float" issue. Now it is up to them to decide whether or not to merge it.

[aeneasr]

Hey @leetal thanks for this! Float64 indeed makes sense because javascript is using 64bit floats always. I think it's ok to increase the minor version with this PR.

Let me know if you want to wait for jwt-go to be merged or just merge this directly and release a new version. Both work for me.

[leetal]

Yeah, I think it is OK for now. It's a later discussion whether or not to
change back to int64. For now it will probably work for more or less
everyone, even if someone actually is using the raw values or not.
It will probably be a while until jwt-go merge the change. If ever.. ;)

[otraore]

Looking forward to seeing this merged in, gives me a reminder I have to update to the new jwt-go api on some personal projects

[aeneasr]

Ok, thanks for the hard work!