feat: add rate limit error on unlock page

[lionellbriones]

Description

Added protection against Brute-force in Onboarding-Unlock page.
To prevent brute forcability, we are staggering password failures

• 1st - 3rd failure: No delay
• 4th failure: 30-second delay
• 5th failure: 1-minute delay
• 6th failure: 5-minute delay
• 7th failure: 15-minute delay
• 8th failure: 30-minute delay
• 9th failure: 45-minute delay
• 10th failure: 1-hour lockout
• more than 10th failure: Incremental lockout (up to 1 day)
• After 1 day(24 hr), its 24hr lockout on every attempt*

Related issues

Fixes:

Manual testing steps

1. Log into existing wallet with the Social Login
2. Enter incorrect passwords for multiple times

Screenshots/Recordings

Before

After

rate-limit.mov

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.