feat: autofill name field on OAuth signup

[jjinendra3]

Proposed Changes

This PR enhances the OAuth signup experience by including the profile scope in Google OAuth, ensuring that user's name is retrieved correctly. Additionally, it extends the fix to other OAuth providers, pre-filling the name field on SetUsernameView when available. This aligns with the future scope outlined in the previous PR.

Issue(s)

• Closes bug: Missing Name Prompt for New Users Signing in via Google Auth #6138
• Refer to the (PR Comment) and the (Issue Comment) for additional context.

How to Test or Reproduce

1. Sign up using any OAuth provider.
2. After successful authentication and 2FA (if enabled), you'll be redirected to SetUsernameView.
3. The name field will now be pre-filled if the OAuth provider provides this information, allowing users to modify it as needed.

Screenshots

(Test Flow with a New Email ID to Simulate OAuth Signup)

Types of Changes

• Bugfix (non-breaking change that fixes an issue)
• Improvement (non-breaking change that enhances an existing function)
• New feature (non-breaking change that adds functionality)
• Documentation update

Checklist

• I have read the [CONTRIBUTING](https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat) doc.
• I have signed the [CLA](https://cla-assistant.io/RocketChat/Rocket.Chat.ReactNative).
• Lint and unit tests pass locally with my changes.
• I have added tests that verify this fix or feature (if applicable).
• I have updated documentation if necessary.
• Any dependent changes have been merged and published in downstream modules.

Further Comments

This update builds upon the previous fix, streamlining the OAuth signup flow by ensuring that user details are retrieved and pre-filled when available. If an OAuth provider does not return a name, the fallback of manually entering it remains in place.

Let me know if there's anything specific you'd like to adjust or improve! 🚀🚀

[diegolmello]

It's virtually the same, but if you do 'email,profile' (with the comma) like it was mentioned here, you won't need encodeURIComponent

[jjinendra3]

Hey @diegolmello , thanks for the reply!

So, my first attempt was to use 'profile,email' as suggested, but it didn't work. Then, I tried 'email,profile', but that didn't work either.

However, encodeURIComponent("profile email") translates to "profile%20email", which is accepted by Google OAuth. Below are the screenshots demonstrating this behavior.

('profile,email')
('email,profile')
(encodeURIComponent("profile email"))

Please lmk your thoughts on this!🚀 :)