Encode encryptedAuthToken in front end

[marcaaron]

Details

This is a necessary step so we can switch off of passing the encryptedAuthToken in the /transition links when moving from OldDot to NewDot. In the changes here we will no longer be url encoding the encryptedAuthToken before sending it via JSON response to Expensify/App. Tested this change and there are no negative effects of "double encoding" since the urls should already arrive urlencoded.

Fixed Issues (Related to)

https://github.com/Expensify/Expensify/issues/178434

Tests

1. Test against current Web-Expensify master (npm run grunt first)
2. Do QA steps

QA Steps

1. Sign up for a new account in OldDot (mobile user agent)
2. Tap "Join"
3. Tap "Set up my company for free"
   
4. Verify NewDot opens up to a workspace
5. Close the workspace window and navigate to the Concierge chat
6. Upload an attachment
7. Verify the attachment is visible
   

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by @jasperhuangg in version: 1.1.3-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[isagoico]

@marcaaron Hello! I think this one needs to be internal QA. We currently don't have access to the 3 options on log in for step 3 (with gmail accounts)

[marcaaron]

Tested and works great feel free to check it off :)

[isagoico]

Thank you so much!

[OSBotify]

🚀 Deployed to production by @chiragsalian in version: 1.1.4-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅