[Homepage email signup] Remove CMS feature toggle and related code in content-build

[randimays]

Description

As part of #19516, we created a CMS feature toggle. When the toggle is ON, the original / current email signup form should show. When the feature toggle is OFF, the new React widget for the email signup form will show.

This ticket will be for removing the CMS feature toggle and the logic in content-build that uses it.

Engineering notes / background

• PR in va.gov-cms for the feature toggle (FEATURE_EMAIL_UPDATE_WIDGET) : VACMS-19516 Email signup widget feature toggle #19653
• PR in content-build to add the container for the React widget and feature toggle: VACMS-19516 Add container and toggle for Email Signup React widget content-build#2342
• PR in vets-website to add the React widget: 19516 Email Signup Widget vets-website#32892

Testing & QA

Scope / Impact analysis

What, if anything, could break as a result of this change?
Engineer should assess this when approaching PR.

Roles / assignments

After functional testing, code review, accessibility review, and design review can happen in parallel.

• Functional testing:
• Code review:
• Design review:
• Accessibility review:
• Product acceptance:

Acceptance criteria

ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and content model when applicable.

• CMS feature toggle is removed (PR reference)
• content-build feature toggle and old signup form code is removed (PR reference)
• Update monitoring documentation to reflect current code locations
• Impact analysis is filled out and QA test plan is updated accordingly
• Does this product have an existing regression test plan?
  • Yes, link: https://docs.google.com/spreadsheets/d/1pxzl5N3SDQIbckJnyigU1RbK_qIGMKKCN0ElksuffxM/edit?pli=1&gid=0#gid=0 - This test plan was used for implementing the new React widget. It can be used as a regression check when we remove the toggle and related code
  • No, regression test plan will be created as part of the work / points in this ticket

[randimays]

Pulled in for Sprint 20

[randimays]

The PR to remove the feature toggle from the CMS was the last piece of code changes, and it was just merged. I just need to make sure it gets successfully removed from the CMS in all environments (tomorrow I believe) and do another testing pass.

[jilladams]

(No CMS deploy today due to code freeze, so this'll go tomorrow.)

[randimays]

Thanks @jilladams I was just coming here to update after I remembered that!

[randimays]

The feature flag has been removed from the CMS in staging and production, and I've successfully validated that the email signup form is still working as expected in production. Closing as complete.