Forgot password backend logic + frontend design

[AbeerDas]

Notion Ticket Link

Reset Password Page Design Implementation

Implementation Description

This PR implements the design for the Reset Password page as specified in the Notion ticket. The functionality includes sending a reset link to the user's email and providing navigation options based on the user's authentication state.

Steps to Test

1. Logout: Run the frontend and backend and then ensure you are logged out
2. Navigate to http://localhost:3000/forgot-password.
   • Expected Result: The page should load successfully.
   • • Should be the same as the figma designs (shown below)

3. Enter the email you use to log in and click "Send reset link...".
   • Expected Result: You should be redirected to a confirmation frame, and the confirmation message should display the email you just entered.
   • • Should look the same as the figma designs (shown below)

4. Click "Not your email?".

• Expected Result: You should be taken back to the previous page.

5. Click "Remember Your Password?".

• Expected Result: You should be redirected back to the main page.

6. After logging in, navigate back to http://localhost:3000/forgot-password.

   • Expected Result: You should be redirected to the Home Page, preventing access to the Forgot Password page while logged in.

   

Review Focus Areas

• Code Standards: Since this is my first pull request, I would appreciate feedback on adherence to coding standards. Are there better practices for using variables/hooks?
• Styling Format: Is the styling format applied in this PR acceptable for future implementations?
• Backend Routes: Does the backend implementation for additional routes meet our standards and expectations?
• Try catch block: ForgotPasswordPage line 34 I wrote setIsEmailSent(false) (little redundant), however I am not sure what else to put there so maybe look into that

Checklist

• My PR title is descriptive and uses imperative tense.
• My commit messages are clear, descriptive, and written in imperative tense. Commits are atomic, and trivial ones are squashed or fixed into more meaningful commits.
• I have run the appropriate linter(s).
• I have requested a review from the Product Lead and relevant developers who have context on this PR or will build upon it.