Hashing based Verification Token Handling

[anshulg954]

Change Description

Try to be precise. You can additionally add comments to your PR, this might help the reviewer a lot.
It is an enhancement functionality where we ask user to input the verification token instead of verifying it with a link.

If you used new dependencies: Did you add them to requirements.txt?

Who did you ping on Mattermost to review your PR? Please ping that person again whenever you are ready for another review.
@noahho

Breaking changes

If you made any breaking changes, please update the version number.
Breaking changes are totally fine, we just need to make sure to keep the users informed and the server in sync.

Does this PR break the API? If so, what is the corresponding server commit?
It did not break anything but a few users complained that our emails landed in spam. It is an update where we try to minimize the landing of emails in spam. Corresponding server PR: https://github.com/automl/tabpfn-server/pull/76

Does this PR break the user interface? If so, why?
No, it enhances the user interface.

Please do not mark comments/conversations as resolved unless you are the assigned reviewer. This helps maintain clarity during the review process.

[anshulg954]

This also fixes the bug in reverify email. @liam-sbhoo

[tabpfn]

See the inline comments

[anshulg954]

Hi,
I have pushed the changes and added comments wherever necessary. Please also check the corresponding PR on server side.

Thanks

[SamuelGabriel]

I have a minor change proposal. The only question I have left: what do we do if a user is not verified and forgot their password? Both in the case they have the access token for their account and if they do not.

[anshulg954]

for

Hi Sam,
In both the cases user can reset the password and then re-login where reverification will take place if the user is not verified.

[SamuelGabriel]

ok, i see. this sounds good :)