Chore: support for brute-force-protection screens

[ankita10119]

Description

Add support for brute-force protection unblock screens to the Universal Login SDK.

Changes

• Enabled brute-force protection screen type exports in auth0-acul-js interfaces that were previously commented out
• Added three new React screen components in auth0-acul-react:
  • brute-force-protection-unblock - Main screen with unblockAccount() action
  • brute-force-protection-unblock-success - Success confirmation screen
  • brute-force-protection-unblock-failure - Failure handling screen
• Exported new screens from auth0-acul-react package index
• Each screen follows the established pattern with context hooks, error handling, and singleton instance registration

Testing

Tested with sample app.

Checklist

• I have added documentation for new/changed functionality in this PR or in auth0.com/docs
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not the default branch

[subhankarmaiti]

@claude

[github-actions]

Claude finished @subhankarmaiti's task —— View job

---

Overall Assessment

❌ This PR has test failures that must be fixed before merging. The test mocks are missing the useChangeLanguage hook export, which will cause test failures.

Summary

The implementation follows the established patterns correctly for adding new screen components. The three new brute-force protection screens (unblock, success, failure) are structured consistently with existing screens. However, there are critical issues in the test files that need to be addressed.

Issues Found

Critical (Must Fix):

• All three test files are missing useChangeLanguage in their hook mocks, but the actual screen modules export this hook. This will cause test failures.

Minor (Should Review):

• Inconsistent type export pattern in screen-properties.ts - lines 78-79 export additional screen-specific types that aren't exported for the main unblock screen on line 77.

What Looks Good

• Screen component implementations follow the exact pattern used by other screens (e.g., reset-password-success.tsx)
• Proper singleton registration with registerScreen
• Correct use of errorManager.withError for the action function
• Type exports are properly added to all necessary files
• Package exports updated correctly in index.ts

---

Tasks

• Read PR diff and understand changes
• Read project documentation for context
• Review new screen components
• Review test files
• Code quality review
• Security review
• Performance review
• Provide inline feedback
• Final assessment

---