Update SupaSocialsAuth to pass scopes and query params to signInWithOAuth

[dannypurcell]

What kind of change does this PR introduce?

Bug fix/Enhancement to SupaSocialsAuth.

What is the current behavior?

Without the scopes and ability to include prompt=consent in the provider OpenID /authorize request, users are never given the opportunity to grant permissions to an app beyond just the ability to sign in.

What is the new behavior?

It is now possible to add scopes and query parameters to SocialsAuth.

SocialsAuth(
  socialProviders: [
    SocialProviders.azure,
  ],
  colored: true,
  redirectUrl: authService.redirectUrl,
  onSuccess: (Session response) {},
  onError: (error) {},
  scopes: '.default',
  queryParams: (promptConsent) ? {'prompt': 'consent'} : {},
)

This example triggers a consent prompt for all permissions the Azure app registration has requested.
https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc#the-default-scope

Additional context

This is a requirement for apps using Azure Active Directory and the Microsoft Graph API unless we want to make an Azure AD admin manually grant permissions through the Azure console any time they change.

[dshukertjr]

Thanks for this! Yes, it would be great if we could support scopes and queryParams for social auth!

Would you be able to update it so that we can pass different scopes and queryParams for each provider?

Maybe we could make scopes type Map<OAuthProvider, String>?, make queryParams type Map<OAuthProvider, Map<String, String>>? so that users can specify different parameters for different OAuth provider?

[dannypurcell]

That makes sense, I'll try it out here in a couple of days and update.

[dshukertjr]

I just updated the PR from my end. Thanks for the amazing contribution!