VACMS-17142: Update service content types post-Service Location migration

[Becapa]

Description

Relates to #17142

Testing done

Manual

Screenshots

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

As a user with administrative access

1. Go to add a VAMC Facility Health Service node (/node/add/health_care_local_health_service) and verify the following fields are not visible:
   • Appointment intro text
   • Appointment lead-in text
   • Are walkins accepted?
   • Is online scheduling available for this service?
   • Phone numbers for appointments
2. Edit a Service Region page (i.e. /node/61786/edit)
   • Add some content to the service location section (Office visits, virtual support, appointment intro text, custom text, ust the facility phone number, other phone numbers, is online scheduling available)
   • Make note of the order of the fields on the page and save the page.
   • Click on the view tab and verify that the order of the page is the same as the edit tab.
3. Edit a VAMC Facility Health Service page
   • Make note of the order of the fields on the page
   • Click on the view tab and verify that the order of the page is the same as the edit tab.
4. Edit a VAMC Facility Non-clinical Service page
   • Make note of the order of the fields on the page
   • Click on the view tab and verify that the order of the page is the same as the edit tab.
5. Edit a VBA Facility Health Service page
   • You may first need to generate a page by filling in all of the required fields and saving.
   • Make note of the order of the fields on the page
   • Click on the view tab and verify that the order of the page is the same as the edit tab.

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

[omahane]

This looks promising, but we need to also account for the service location fields and their display.

Office Visits, Virtual support and Appointments order

Appointments (detailed order)

[omahane]

This looks great, all present and correct.