O3-5425: Validate order dates against patient DOB

[BlessedAmrita]

Description of what I changed

Added DOB lower-bound validation for dateActivated and scheduledDate in OrderValidator.

Since these date fields live on the base Order class, placing the validation in OrderValidator means it automatically applies to all order types: TestOrder, DrugOrder, ReferralOrder, etc. When either date falls before the patient's date of birth, the validator rejects it with a field error. Dates equal to the birthdate are allowed.

Changes:

• OrderValidator.java: Added birthdate lower-bound checks in validateDateActivated() and validateScheduledDate() methods, with null guards for patient and birthdate
• OrderValidatorTest.java: Added 10 test cases (5 per date field) covering before/equal/after birthdate, null date, and null birthdate scenarios
• messages.properties: Added Order.error.dateActivatedBeforePatientBirthdate and Order.error.scheduledDateBeforePatientBirthdate keys

Test scenarios (for each date field):

• Date before patient birthdate → validation error
• Date equal to patient birthdate → no error
• Date after patient birthdate → no error
• Date is null → no error
• Patient birthdate is null → no error

Part of the Date Picker Improvements epic (O3-5424).

Issue I worked on

see https://issues.openmrs.org/browse/O3-5425

Checklist: I completed these to help reviewers :)

• My IDE is configured to follow the code style of this project.
• I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)
• I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.
• All new and existing tests passed.
• My pull request is based on the latest changes of the master branch.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sagarkhandagre998]

@BlessedAmrita, apologies for the earlier incorrect feedback. After reviewing the maintainer's guidance more carefully, your approach of validating dates against the patient's date of birth is actually the right direction. The maintainer confirmed that the patient's DOB is the natural lower bound for these dates, which inherently catches single-digit year entries like "02/01/1" since year 1 will always be before any real patient's birthdate.

[sagarkhandagre998]

One edge case to consider —> in OpenMRS, a patient's birthdate can be estimated (birthdateEstimated = true), When this is the case, the stored birthdate is not an exact date —> it is a synthetic value calculated from the patient's approximate age.

Would it could cause false rejections?

Reference - visitValidator

[sagarkhandagre998]

Same here.

[sagarkhandagre998]

You can remove the hard coded message.