Bug Report: Invalid Birth Year Accepted During Signup

### 🐛 Describe the bug

## Description

During testing of the signup process, I observed that the application allows users to select a future birth year (e.g., 2026).

The system does not validate whether the selected birth year is logically valid or meets minimum age requirements.

This may result in unrealistic user profiles and inaccurate age-related logic.

---

## Steps to Reproduce

1. Open the mobile application.
2. Navigate to the **Sign Up** page.
3. Enter required details.
4. Select a future birth year (e.g., 2026).
5. Complete the registration process.

---

## Expected Behavior

- The system should not allow selecting a future birth year.
- The birth year must be less than or equal to the current year.
- If the platform has a minimum age requirement (e.g., 13 or 18), validation should enforce it.
- A clear validation message should be displayed.

---

## Actual Behavior

- The application accepts a future birth year (e.g., 2026).
- The account is created successfully without validation errors.

---

## Impact

- Invalid user age data in the system.
- Potential issues with age-restricted features.
- Reduced data integrity.

---

## Suggested Improvement

- Add frontend and backend validation for birth year.
- Restrict future dates.
- Enforce minimum age requirements if applicable.

## Screenshot
https://github.com/user-attachments/assets/7d1ab52c-e19a-4d23-af1c-cece3b7ee38b