VACMS-16545: Patch smart_date recurring date validation.

[Becapa]

Description

Closes #16545 .

QA steps

As a user that can create/edit events

1. Create or edit an event and fill in all required fields.
   • Validate that the event can be saved when the Make recurring checkbox is checked and the Until date comes after the Start date.
2. Edit the event again (or create another new event)
   • Validate that the event shows an error upon saving when the Until date comes before the Start date.

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[dsasser]

Looks good!

[jilladams]

Daniel previously approved; merging main back in un-approved but no other code changes were made. So: I'm rubber stamping to unblock since Daniel's now without power. If that doesn't work, it'll roll to tomorrow and that's ok.