Make custom redirect_uri_match_fun work with authorization validations

[davejachimiak]

Working with @blatyo, we discovered that custom
redirect_uri_match_funs were not being invoked during the
authorization phase. This fixes that by passing the config from
RedirectURI.valid_for_authorization? to matches?.

[danschultzer]

Thanks! I just fixed up this PR by deprecated matches?/2 and returning the test to matches?/3 method since this is where the redirect_uri_match_fun logic is used. The deprecation warning ensures that all methods calls to matches?/3 are correct now, so it's no longer necessary to test valid_for_authorization?.

[danschultzer]

v0.5.3 released 🚀

[danschultzer]

For some reason hex doesn't publish docs, and just returns 502 error. I'll wait an hour and try again.

[danschultzer]

v0.5.3 released, hex publish still didn't work properly, but doing mix hex.publish docs after the release properly added the docs.

[davejachimiak]

Thanks @danschultzer!

[blatyo]

Hey @danschultzer, thanks for this. I just tried to pull 0.5.3 from hex and got:

** (Mix) No matching version for ex_oauth2_provider ~> 0.5.3 (from: mix.exs) in registry

The latest version is: 0.5.2

In the elixir slack hex channel, it seems like they were having issues with the registry over the weekend. They're recommending people publish a new version to get around it.

[danschultzer]

Released v0.5.4, and I've retired v0.5.3. Thanks for letting me know 😄