Removes My VA Health from VAOS direct schedule facility page

[ryanshaw]

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

⚠️ TeamSites ⚠️

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

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

This PR removes the My VA Health links from the VA facility page in within the direct schedule flow. Previously, the links were removed for a specific type of care in this PR

Related issue(s)

• Remove links to My VA Health from DS location page va.gov-team#96902

Testing done

• Manual local testing replacing local mocked responses with staging responses for [email protected]
• Unit tests

Screenshots

Before	After

Acceptance criteria

• Regardless of whether or not the vaOnlineSchedulingOhDirectSchedule flag is on or off, there should be no My VA Health link next to any OH facility on the VA facility page within the direct scheduling flow

Quality Assurance & Testing

• I updated 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

[vbahinwillit]

LGTM!