Check for unvalidated accounts and change in password flow

[chiragsalian]

HOLD until the web-e and auth PRs go live i.e,

• https://github.com/Expensify/Auth/pull/5382 AND
• https://github.com/Expensify/Web-Expensify/pull/30507

Details

Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/156783

Tests

1. On dev first go to ./script/sql.sh and run delete from notifications to begin on a clean slate.
2. Go to e.cash
3. Enter your Email. Confirm you see the forgot button,
   
4. Click it. For dev run php /vagrant/Web-Expensify/script/notifyall.php from within vssh.
5. Check the email. Confirm its magic link is of the format <baseUrl>/setpassword/<code>. Don't click it just yet.
6. Confirm the UI for the existing e.cash tab has updated to be,
   
7. Open console. Click "Resend Link" and confirm you see the console log "Account forgot password: Sending reset password link."
8. Click the link from the email at step 5 and confirm you are redirected to set your password. Set your password and confirm you are logged in. Log out.
9. Now attempt to log into e.cash using an account that's not validated.
10. Confirm you are redirected to this UI
    
11. Open console and click "Resend link". Confirm you see the log "Account is unvalidated: Sending validation link."
12. For dev run php /vagrant/Web-Expensify/script/notifyall.php from within vssh. You might have to run update notifications set json = json_set(json(notifications.json), '$.to', '<yourExpensifyEmail>'); if the unvalidated email does not belong to expensify since we only send emails out to expensify.
13. Check the email and confirm its link is of the format <baseURL>/setpassword/<code>. Click it and confirm you can set your password and you are logged in once done.

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

[chiragsalian]

Accidently added pullerbear a second time so i removed robert as reviewer since i think just two would suffice. Manually added stites since i think you may have worked on this flow for e.cash

[pecanoro]

Not <email> sounds weird to me hehe, but if that's the copy we chose 🤷‍♀️

[chiragsalian]

The related auth code is live and the web-e code is on staging. It should be on production tomorrow and then this PR will be off HOLD.

[chiragsalian]

Off HOLD since the related PRs are live. Ready for reviews / merge.

[pecanoro]

@stitesExpensify I approved already so it's up to you!

[stitesExpensify]

Is there a reason we're printing this to the console? Seems unnecessary IMO

[chiragsalian]

Yes, because when you click "resend link" its hard to tell which flow is being called. You can check the network tab for this but its easier with two console.debug as can be seen in test steps 7 and 11. Just makes life easier when you want to debug.