Date validations to prevent invalid dates like 6/1/20000

[marc]

What github issue is this PR for, if any?

Resolves #5646

What changed, and why?

Added date validations to avoid bad dates like 6/1/20000:

CourtDate

• date - no earlier than 1/1/1989. No later than 1 year in the future.
• court_report_due_date - ignored

CasaCase

• birth_month_year_youth —> range from 1989 to today
• court_report_due_date —> ignored
• court_report_submitted_at —> set by app
• date_in_care —> range is from 1989 to today

CaseContact

• occurred_at —> already validates can’t be in future, added 1989 minimum

LearningHour

• occurred_at —> already validates can’t be in future, added 1989 minimum

MileageRate

• effective_date —> no earlier than 1/1/1989. No later than 1 year in the future.

OtherDuties

• occurred_at —> no earlier than 1/1/1989. No later than 1 year in the future.

PlacementsStartedAt

• Placement_started_at —> no earlier than 1/1/1989. No later than 1 year in the future.

User

• date_of_birth —> range from 1920 to today

UserReminderTime - added by #3735 but not used anywhere. Currently no orgs use SMS anyways so we are fine ignoring this
case_contact_types —> ignored
no_contact_made —> ignored

How is this tested? (please write tests!) 💖💪

Updated specs for models and manually tested UI.

Screenshots please :)

Sample validation for new court dates:

Feelings gif (optional)

😀 😀

Worked on by @yyelleww70 and @marc .

[compwron]

looks great, please fix failing tests and then we can merge :)

[elasticspoon]

LGTM.

Just a thought (don't actually change anything in response to this) I wonder if a better arbitrary date instead of 1989 should have been 22 years ago (I think 21 years is the cap on age in foster care).

[compwron]

24 days cap