feat: password crack time logic

[nicolewu0901]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have run the tests for the backend and frontend depending on what's needed for my changes as described in the testing section of the contributing guide

---

Description

Description of the proposed change...
This pull request implements Issue #1549, replacing the qualitative password strength labels ("Weak", "Strong", etc.) with a quantitative "Time to Crack" estimation. This change aims to provide users with more tangible feedback regarding their security.

Related issue

• #ISSUE_NUMBER
• Closes Change message about how strong the password is in auth routes to be how long it would take to crack the password #1549

[netlify]

❌ Deploy Preview for activist-org failed. Why did it fail? →

Name	Link
🔨 Latest commit	acf0d5e
🔍 Latest deploy log	https://app.netlify.com/projects/activist-org/deploys/6994f2d63720ca00074411df

[github-actions]

Thank you for the pull request! ❤️

The activist team will do our best to address your contribution as soon as we can. The following are some important points:

• Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
• If you're not already a member of our public Matrix community, please consider joining!
  • We'd suggest that you use the Element client as well as Element X for a mobile app
  • Join the General and Development rooms once you're in
• Also consider attending our bi-weekly Saturday developer syncs!
  • Details are shared in the Development room on Matrix each Wednesday before the sync
  • It would be great to meet you 😊

Note

activist uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the TypeScript, pytest and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[github-actions]

First PR Commit Check

• The commit messages for the remote branch of a new contributor should be checked to make sure their email is set up correctly so that they receive credit for their contribution
  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo (can be set with git config --global user.email "GITHUB_EMAIL")