Fix reset PasswordToken

[charlesBochet]

Bug Description

We are facing a bug in case recaptcha is enabled.
To reproduce:

• Create your recaptcha: https://www.google.com/recaptcha/about/
• update your server .env with the following variables:

CAPTCHA_SECRET_KEY=REPLACE_ME
CAPTCHA_SITE_KEY=REPLACE_ME
CAPTCHA_DRIVER=google-recaptcha

• Go to the login page, enter an existing user email and hit 'Reset your password'.

• Add a console.log in emailPasswordResetLink in auth.resolver.ts to get the token that would be sent by email if you don't have the mailer setup

• Browse: /reset-password/{passwordToken}

• Update the password:

• See that the token is invalid

You should see two calls in your developer network tab. A successful one to update the password and another to log you in. This 2nd call (Challenge) does not have the captcha token provided. It should be

Fix

• Refreshing the token on page load
• providing it to the Challenge graphql call

[greptile-apps]

PR Summary

This pull request addresses a bug related to reCAPTCHA during the password reset process by ensuring the captcha token is refreshed and included in subsequent requests.

• Updated packages/twenty-front/project.json to increase --max_old_space_size for Node.js from 5000 to 6000 for storybook:build.
• Modified packages/twenty-front/src/effect-components/PageChangeEffect.tsx to request a fresh captcha token on the password reset page.
• Enhanced packages/twenty-front/src/pages/auth/PasswordReset.tsx to fetch and include a reCAPTCHA token in the signInWithCredentials call.
• Deleted packages/twenty-server/src/engine/core-modules/auth/dto/password-reset-token.input.ts, removing the PasswordResetTokenInput class.

_{4 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}