Toxic Exposure - Add custom BE validation for Add Conditions

[sethdarragile6]

Issue Description

This story is a subset of a larger story, 79938 Toxic Exposure - Schema for all TE fields to Form526 vets JSON schema, currently targeted for the Iteration #4. Because the Add Conditions JSON from the FE (toxicExposureConditions, see contact) generates dynamic properties, it was found on an earlier ticket that our currently implementation of JSON Schema on the BE can not handle it. Therefore, some sort of custom validation (at the submit_all_claim level) should be in place to cover that gap.

---

Tasks

• [ ] Add custom validation of the toxicExposureConditions FE node

Acceptance Criteria

• [ ] The toxicExposureConditions FE node is validated before the claim is saved, returning an error to the caller if it fails

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [ ] Attached to an Epic (what body of work is this a part of?)
• [ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
• [ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [ ] Labeled with Type (bug, request, discovery, documentation, etc.)

[alatempa24]

This is a nice to have - moving to Post MVP epic