Identity age validation

[Zykem]

Description

This PR refactors the age validation logic. It replaces the previous LowestYear and HighestYear with MinAge and MaxAge, making the age validation more dynamic and easier to configure. The logic now calculates the minimum and maximum valid birth years based on the current year and the configured MinAge and MaxAge.

---

Motivation

This PR was inspired by #1626 Pull Request, where a recent change only adjusted the MinYear configuration value. Rather than continuing with static year values, I aimed to provide a more flexible solution by introducing age-based configuration. This allows users to specify the age range directly, making it clearer and easier to manage, especially when maintaining the age validation across multiple versions.

---

Implementation Details

• The Config.LowestYear and Config.HighestYear have been replaced by Config.MinAge and Config.MaxAge in the main config file.
• The checkDOBFormat function has been updated to dynamically calculate the valid birth years based on the current year and the configured MinAge and MaxAge
• A simplified leap year check has been incorporated to ensure that 29.02 (Feb. 29) is validated properly for leap years (instead of having this unreadable logic in the same function)

This refactor improves clarity, flexbility and scalability, allowing the age range to be updated without changing hardcoded year values.

Usage Example

Config.MinAge = 15
Config.MaxAge = 45

Now, instead of adjusting the LowestYear and HighestYear, users can directly specify the minimum and maximum ages.

PR Checklist

• [] My commit messages and PR title follow the Conventional Commits standard.
• [] My changes have been tested locally and function as expected.
• [] My PR does not introduce any breaking changes.
• [] I have provided a clear explanation of what my PR does, including the reasoning behind the changes and any relevant context.

[Kenshiin13]

LGTM, thanks!