Feathers Client reAuthenticate should check window.location before localstorage for OAuth logins

[nathanbrizzee]

In my testing of changing OAuth provider logins, I've run into the following scenario. If I sign in with Microsoft as an OAuth provider, then sign in with Google as an OAuth provider, I end up getting back the user object for the Microsoft account, not the Google account. The reason for this is because local storage is checked before window.location and since I have a token from the previous OAuth login in localstorage, even though I successfully authenticated with Google, it signs me in with the Microsoft token. The reason why is because of this line:

feathers/packages/authentication-client/src/core.ts

Line 146 in 21d6aaa

authPromise = this.getAccessToken().then((accessToken) => {

I propose this line be changed to something like the following to ensure OAuth tokens take priority over localstorage tokens:

...
 authPromise = this.getFromLocation(window.location)
  .then((accessToken) => {
   if (accessToken) {
    return accessToken
   } else {
    return this.getAccessToken()
   }
  })
  .then((accessToken) => {
    if (!accessToken) {
      return this.handleError(new Error('No accessToken found in storage'), 'authenticate')
    }
...