Fix cached scopes when using detailed response mode

[stevehobbsdev]

Changes

This PR ensures that the scopes as returned from the token endpoint are recorded in the cache by handleRedirectCallback. This fixes an issue where using getTokenSilently({ detailedResponse: true }) immediately after a login would yield no scope property, despite being returned by the endpoint, but are then populated later after a page refresh (thanks to checkSession).

The PR also addresses a minor issue where detailedResponse was being sent as a custom property to the /authorize and /oauth/token endpoints.

References

Fixes #823

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed