Remove TERA conditional logic from the Health Care Application

[longmd]

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

Now that the TERA questions are permanent in the health care application, we can remove the feature toggle and any other unnecessary logic from the code. This PR removes the conditional logic and makes the questions permanent.

Related issue(s)

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

Acceptance criteria

• No unnecessary logic exists in the codebase

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
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution

[JoshingYou1]

LGTM!

[coope93]

LGTM. I assume we want to remove the toggle from featureFlagNames.json and the vets-api features.yml file in a future PR as well?

[longmd]

Correct! These will be separate PRs to keep this work inside the CD pipeline.