VACMS-19967: Remove phone toggle post migration

[omahane]

Description

Relates to #19967
Relates to #19969

Testing done

Manually
Cypress

Screenshots

QA steps

Set up QA Content Publisher

• Log in as an admin
• Assign the following roles to the QA Content Publisher
  • Content publisher
  • Content creator - VAMC
• Assign the following section to QA Content Publisher
  • Boston VA health care

Check VAMC System Billing and Insurance

• Log in as QA Content Publisher
• Go to VAMC System Billing and Insurance
• Confirm that only one phone number field is present
• Click edit
• Confirm that only one phone number field is present

Check VAMC Facility

• Go to Jamaica Plain VA Medical Center
• Confirm that only one Mental health phone number is present
• Click edit
• Confirm that only one Mental health phone number field is present

Check Staff Profile

• Go to Jeremiah Elsinger staff profile
• Confirm that only one phone number is present
• Click edit
• Confirm that only one Mental health phone number field is present

Regression tests

• Cypress
  • health_care_local_facility.feature
    • has a step for adding a Mental health phone number
  • person_profile.feature
    • has a step for adding a phone number

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[omahane]

@eselkin I am getting a content-build-gql error in this PR because the query is looking for the old phone number field:

Screenshot of the error

The log file excerpt

20241216-content-build-gql-error.txt

(cc @jilladams @Agile6MSkinner This is blocked until the the content-build issue is resolved)

[eselkin]

@eselkin I am getting a content-build-gql error in this PR because the query is looking for the old phone number field:

Screenshot of the error

## The log file excerpt [20241216-content-build-gql-error.txt](https://github.com/user-attachments/files/18156211/20241216-content-build-gql-error.txt)

(cc @jilladams @Agile6MSkinner This is blocked until the the content-build issue is resolved)

Maybe it's not in main yet, let me check... Did you release main/main?

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[dsasser]

Changes look good (again!).

[github-actions]

Checking composer.lock changes...

[va-cms-bot]

Tugboat has finished building the preview for this pull request!

Links:

• https://pr20101-3l0mof51ngr1hdlfew7vcusi6oi5unbr.ci.cms.va.gov
• https://cms-3l0mof51ngr1hdlfew7vcusi6oi5unbr.ci.cms.va.gov
• https://web-3l0mof51ngr1hdlfew7vcusi6oi5unbr.ci.cms.va.gov
• https://storybook-3l0mof51ngr1hdlfew7vcusi6oi5unbr.ci.cms.va.gov
• https://next-3l0mof51ngr1hdlfew7vcusi6oi5unbr.ci.cms.va.gov

Dashboard:

• https://tugboat.vfs.va.gov/6760334642f7e413238b6975

[va-cms-bot]

Cypress Accessibility Violations

/test-data-blanditiis

ID: button-name
Impact: critical
Tags: cat.name-role-value, wcag2a, wcag412, section508, section508.22.a, TTv5, TT6.a, EN-301-549, EN-9.4.1.2, ACT
Description: Ensure buttons have discernible text
Help: Buttons must have discernible text
Nodes:

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Page introduction' field" data-proofing-help="Add an introduction that helps visitors understand if information on the page is relevant to them."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: .field--name-field-intro-text-limited-html > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Generate a table of contents from major headings' field" data-proofing-help="By checking this box, all h2's below this point on the page will be linked with with anchor links. This helps users navigate content on very long pages. Do not check this box unless there is at least 2 h2's on the page.">
  Impact: critical
  Target: .field--name-field-table-of-contents-boolean > .field__label > .proofing-element-help[role="tooltip"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"

• HTML: <button class="proofing-element-help" role="tooltip" data-proofing-help-title="About 'Main content' field" data-proofing-help="The main body of the page, which appears below the featured content."> <span aria-hidden="true">i</span> </button>
  Impact: critical
  Target: button[data-proofing-help-title="About 'Main content' field"]
  Summary: Fix any of the following:
  Element does not have inner text that is visible to screen readers
  aria-label attribute does not exist or is empty
  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
  Element has no title attribute
  Element does not have an implicit (wrapped) <label>
  Element does not have an explicit <label>
  Element's default semantics were not overridden with role="none" or role="presentation"