Schema for all Toxic Exposure fields to Form526 vets JSON schema

[christinec-fftc]

Issue Description

Add TE fields to Form526 validation (vets JSON schema) schema Scope of this ticket - The contract for all remaining fields being added as part of Toxic Exposure initiative

Current state - FE and BE use JSONSchema to validate New state - FE needs to point to patterns to validate to decouple the JSON schema from FE changes

---

Notes

We added a lot of the validation already with the XX date issue. PR for vets-json-schema here We can use this as an example for the mapped keys.

fields that need to be added

conditions # *can we do this? these are dynamic keys
gulfWar1990  # mapped keys
herbicide # mapped keys
otherHerbicideLocations.description  # front-end regex
otherExposures # mapped keys
specifyOtherExposures.description # front-end regex

---

Tasks

• [ ] Reference the contract between FE and BE for schema validation
• [ ] Add TE fields to vets-json-schema (for BE validation).
• [ ] Add LH Regex pattern for herbicides other locations and additional hazard's specify other exposure
• [ ] Verify that FE and BE validation schema is compatible

Acceptance Criteria

• [ ] Add TE fields to JSON schema

---

Related links

• [ ] Original spike story

  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.)

[christinec-fftc]

@sethdarragile6 please help us prep this story for refinement

[pacerwow]

Is this launch blocking?

[aurora-a-k-a-lightning]

We added these fields to vets-json-schema already. We now just need to put in the difference.