65089 post toxic exposure launch cleanup

[christinec-fftc]

Are you removing, renaming or moving a folder in this PR?

• No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

• No
• Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• Any logic that was preventing toxic exposure pages from displaying is removed
• Any unit or e2e tests referencing this logic is removed

flipper removal in #99346

Related issue(s)

department-of-veterans-affairs/va.gov-team#65089

Testing done

• Manually verified 526 form with toxic exposure is working as expected
• Updated unit and e2e tests accordingly

Screenshots

n/a. no visual changes

What areas of the site does it impact?

526ez

Acceptance criteria

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

[tommasina-va]

Hooray! LGTM 👏🏻

[sethdarragile6]

LGTM!