[TTAHUB-3452] Fix comm date validation

[thewatermethod]

Description of change

The issue here is that the validation on the frontend (can we parse a valid date from what the user enters using the momentjs library?) normally combines with postgres date columns to standardize the saved format. Since we are saving the date here to a JSON field, the date field can contain any arbitrary value that moment can figure out. This change preempts the save and create communication log services to use moment's formatting to save whatever date it has parsed from user input.

How to test

Save a date in a non MM/DD/YYYY format in the communication date field in the comm log. Save: the value in the UI and the database is corrected.

Issue(s)

• https://jira.acf.gov/browse/TTAHUB-3452

Checklists

Every PR

• Meets issue criteria
• JIRA ticket status updated
• Code is meaningfully tested
• Meets accessibility standards (WCAG 2.1 Levels A, AA)
• API Documentation updated
• Boundary diagram updated
• Logical Data Model updated
• Architectural Decision Records written for major infrastructure decisions
• UI review complete

Before merge to main

• OHS demo complete
• Ready to create production PR

Production Deploy

• Staging smoke test completed

After merge/deploy

• Update JIRA ticket status

[GarrettEHill]

that seems to be the fix for https://jira.acf.gov/browse/TTAHUB-3453