Inconsistent behavior of providers using GoogleProvider() and AppleProvider()

### Is there an existing issue for this?

- [X] I have searched the existing issues and found no duplicates.

### What plugin is this bug for?

Firebase UI OAuth Google, Firebase UI OAuth Apple

### What platform(s) does this bug affect?

Android, iOS

### List of dependencies used.

flutter pub deps -s list

  firebase_core: ^2.10.0

  firebase_auth: 4.12.1

  firebase_ui_auth: ^1.1.8

  firebase_ui_oauth: ^1.1.8

  firebase_ui_oauth_google: ^1.0.15

  firebase_ui_oauth_apple: ^1.0.15

### Steps to reproduce

Setup the standard SignInScreen of FirebaseUIAuth with successfully configured providers GoogleProvider(clientId:) and AppleProvider() and login the existing user with the signInAnonymously method beforehand.

On the SignInScreen, using the "Sign in with Apple" option, the account is permanently created in the user management and successfully upgraded / linked to the provider. Logging in on another device after that (while being again anonymously logged in before, too) the anonymous login is overwritten in favor of the recently created account, linked with the apple provider.

However, trying the same using the GoogleProvider, the behavior seems to differ and I hope someone can either explain this behavior to me or look into the issue.

### Expected Behavior

It is expected that the GoogleProvider works exactly the same as the AppleProvider in case of Sign-up, linking and especially signing in again on a different device using the same credentials.

### Actual Behavior

Signing in with the GoogleProvider on another device leads to an "credentials-already-in-use" error of the framework, indicating that the credentials belong to another account and therefore cannot be linked to another (anonymous) user.

In contrast to AppleProvider, the GoogleProvider doesn't seem to recognize that the user tries to sign-in with existing credentials, so it seems impossible to sign-in with GoogleProvider like it is with AppleProvider.

Same holds true if you log out of your existing account, being automatically logged in anonymously again immediately by the app, then trying to sign-in using the same credentials used some minutes ago.

### Additional Information

_No response_

Commencez par reproduire le flux décrit avec SignInScreen, GoogleProvider(clientId:) et AppleProvider(), en vous connectant d’abord de manière anonyme sur un appareil, puis en utilisant les mêmes identifiants sur un autre. Comparez le comportement des providers lors de la liaison et de la connexion, y compris l’erreur credentials-already-in-use ; le travail est terminé lorsque Google gère les identifiants existants de manière cohérente avec Apple sans tenter de les lier incorrectement à un nouveau compte anonyme.

Rédigé par le modèle d'indexation à partir du texte de l'issue.