Fix #1222: Handle unregistered email in forgot password route with 404

[sudip22-p]

Forgot Password Functionality - Error Handling Update

Description

This update improves the error handling and response structure for the forgot password functionality:

• Email input validation: Returns 400 Bad Request for invalid emails.
• Returns a 404 Not Found if the provided email is not registered.
• Used upsert: true for reset token updates to ensure token is either created or updated correctly.
• Wrapped the entire function in a try-catch block to handle unexpected errors and return 500 Internal Server Error when needed.

Related Issues

-#1222

Steps to Test

1. Test with a registered email:

   • Ensure a reset token is generated, and an email is sent to the user.

2. Test with an unregistered email:

   • Confirm that a 404 Not Found response is returned with the message:
     • "No account with this email has been registered."

3. Test with an invalid email format:

   • Verify a 400 Bad Request response is returned with the message:
     • "Invalid email."

Checklist

• I have tested these changes.
• I have updated the relevant documentation.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings or errors.
• The title of my pull request is clear and descriptive.