Add rate limiting to authentication endpoints

[Harxhit]

Summary

Add rate limiting to authentication endpoints to protect against abuse and reduce unnecessary load on the backend.

Contexts

Currently, authentication routes such as login and registration do not have dedicated rate limiting. This may allow excessive requests, brute-force attempts, or credential stuffing attacks.

Tasks

• Identify authentication-related routes
• Configure route-level rate limiting
• Return appropriate error responses when limits are exceeded
• Verify existing functionality is unaffected

Acceptance Criteria

• Rate limiting is applied to authentication endpoints
• Excessive requests are blocked with a proper response
• Tests added
• docs updated (if needed)

Area

backend

Difficulty

easy

[github-actions]

Hi @Harxhit,

Thanks for opening this issue.

Please reply with one of the following areas so the issue can be routed to the appropriate team member:

- /backend
- /web
- /mobile
- /devops

Once an area is selected, the corresponding label will be added automatically.

[Harxhit]

/backend

[github-actions]

The issue has been classified as backend.

@Harxhit, please review and triage this issue when available.

The backend label has been applied and the issue has been routed accordingly.