Toxic Exposure: Remove dates from LH submit request for unselected location/hazard options

[sethdarragile6]

Issue Description

When a user selects a particular hazard or location option (e.g. "Iraq"), enters a partial date for the option, but then goes back and deselects that option- this partial date (e.g. "XXXX-03-XX") makes it to the backend as-is, then on to the submit request to Lighthouse (where it results in a non-retryable error). We should also guard against the possible scenario of submitting full, valid dates for options that were unselected.

---

Tasks

• Modify transform_multiple_exposures (link) to filter out dates where the option was set to false
• Write unit tests against this scenario

Acceptance Criteria

• Dates associated with unselected location/hazard options are omitted from the LH submit API request

Related Links

• slack thread
• slack thread

---

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