[SDK-1417] Customizable default scopes

[stevehobbsdev]

Description

Adds the ability to customize the default scopes that are used with authorization requests.

Today, the SDK defaults these scopes to openid profile email plus whatever the developer specifies. However, there is a need to customize what those defaults are.

This PR adds a new advancedOptions object to the SDK configuration were the defaults can be specified.

With this implementation, the openid scope is still always applied regardless of the default scope configuration. However, the developer has the ability now to remove profile and email scopes should they wish.

This PR also refactors out the getUniqueScopes mock so that the actual implementation is used in all cases. To do this, getUniqueScopes has been pulled out of utils.ts and moved to a new module scope.ts. Tests moved as well to match.

References

This PR is customized from #389 and takes precedence.

Testing

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation for new/changed functionality in this PR or in auth0.com/docs
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not master

[adamjmcgrath]

You should be able to do

import * as scope from '../src/scope';

beforeEach(() => {
  jest.spyOn(scope, 'getUniqueScopes');
});

it('should do something', () => {
  // do something
  expect(scope.getUniqueScopes).toHaveBeenCalledWith(...);
})

[stevehobbsdev]

I did try this but it wasn't working thanks to doing jest.resetAllMocks() as well. Turns out you need to manually restore a spy, as resetting a spy results in a function with no return value.

However, I don't believe the tests need to assert this any more as we're already asserting that the scopes are correct in assertions for cache.get, utils.createQueryParams, etc. We already have a test suite that asserts usage of getUniqueScopes too.

I will leave the spy setup in though in case we want to mock it in the future and we forget about this problem ☝️

[adamjmcgrath]

(optional) since split takes a regex you could simplify to:

return dedupe(scopes.join(' ').split(/\s+/).join(' '));

[stevehobbsdev]

Also needed a trim() in there, but yes - implemented this.

[adamjmcgrath]

(optional) now we have Set, you can do:

const dedupe = arr => [...new Set(arr)]

[stevehobbsdev]

I had to change it to [...(new Set(arr))], but yes - using Set here makes sense now that we have the polyfill available.

However, doing this requires us to use the --downlevelIteration compiler flag which adds a bit of bloat to the code. The code can be changed to Array.from(new Set(arr)) which does not require this flag. Possibly a little more readable too.