Business API: Add Missing Contact Point Email Validation

### Description:
As an API user posting a filing, I want to get appropriate validation errors if I try and put in a contact point email address that would not pass the frontend validation, so that my saved data is accurate and reliable and will not cause issues if used again through the frontend.

On the frontend, the Contact Point email field is validated for proper email format and leading/trailing whitespace before submission. Ex: "a@b.c", " test@example.com" (leading space), or "test@example.com " (trailing space) all pass the amalgamation API but would be rejected by the frontend. _(pls ignore the req for leading/trailing spaces in this ticket)_

**List of filings where contactPoint is required but email is not validated:**
- [ ] Alteration
- [ ] Amalgamation Application
- [ ] Change of Registration
- [ ] Continuation In
- [ ] Correction
- [ ] Incorporation Application
- [ ] Registration
- [ ] Restoration

**QA Notes**
- Ensure regression of amalgamation application through the frontend — ensure email address saves properly
- Posting an amalgamation application through the API works as expected
- Posting email address formats that would not pass the frontend cause the API to return an appropriate error message about invalid format:
- Invalid format e.g. "a@b.c"
- Leading whitespace e.g. " test@example.com"
- Trailing whitespace e.g. "test@example.com "