POLIO-1776: subactivity validation

[quang-le]

What problem is this PR solving? Explain here in one sentence.

Related JIRA tickets : POLIO-1776

Self proofreading checklist

• Did I use eslint and black formatters
• Is my code clear enough and well documented
• Are my typescript files well typed
• New translations have been added or updated if new strings have been introduced in the frontend
• My migrations file are included
• Are there enough tests
• Documentation has been included (for new feature)

Doc

NA

Changes

• Add front-end validation for subactivities dates:
  • start and end-date should be after round start date
  • lqas and im dates should be after subactivity end date
• Added round dates to formik values to be able to access them for validation
• Remove round dates before calling subactivities API
• fix some TS typing

How to test

Go to polio campaigns, create a sub-activity with dates that are all wrong

Print screen / video

Notes

• Validation was left front-end only on the basis that we don't validate round dates back-end side

Follow the Conventional Commits specification

The merge message of a pull request must follow the Conventional Commits specification.

This convention helps to automatically generate release notes.

Use lowercase for consistency.

Example:

fix: empty instance pop up

Refs: IA-3665

Note that the Jira reference is preceded by a line break.

Both the line break and the Jira reference are entered in the Add an optional extended description… field.