Removes Old Feature Flags - Sa 81559 - SA-81565 - SA-81572- SA-81578

[bradbergeron-us]

Summary

Removes old feature flags established in production

• Get Form Help Text on Original Claims
• Text Notifications Disclaimer
• Original Claims Applicants who live on a military base
• Original Claims Form Introduction Page title
• When no benefit is Relinquished on an original claim application, we send a NotEligible value by default for automation.
• Linking to Paper Form on the Introduction Page

Related issue(s)

Testing done

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

	Before	After
Mobile
Desktop

What areas of the site does it impact?

TOE 1990E MEB 1990EZ

Acceptance criteria

Quality Assurance & Testing

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

Error Handling

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

Authentication

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

:warning: Team Sites (only applies to modifications made to the VA.gov header) :warning:

• [ ] The vets-website header does not contain any web-components
• [ ] I used the proxy-rewrite steps to test the injected header scenario
• [ ] I reached out in the #sitewide-public-websites Slack channel for questions

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?

[github-actions[bot]]

This PR is stale because it has been open 120 days with no activity. It will recieve a stale label every day for 14 days before being closed unless it recieves a comment or the stale label is removed.

[bradbergeron-us]

Leaving open for a little longer for referencing