fix(parseDate): Prevents 3-digit year from being accepted as valid (#2483)

[imShubh03]

What I did

1. Fixed an issue where 3-digit years (e.g., 27/12/202) were incorrectly parsed as valid dates.
2. Ensured that years below 1000 are treated as invalid.
3. Added a check to return undefined for such cases.

@tlouisse Please review and verify.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6cf36c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}