VACMS-15559 Migration of service location data to paragraphs

[swirtSJW]

Description

Relates to #15559

Testing done

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 admin

1. Go to the tugboat terminal

   • enter drush scr ./scripts/content/VACMS-15559-migrate-service-location-from-node-to-paragraph.php
   • You should see it progressing in groups of 25.
     
   • Revisit it ~2hrs later
   • You should see the following message. (the numbers might differ slightly based on current content.)
     

2. Facility service with multiple service locations https://pr16911-frzioxcuceuh23pjuqcftuoyfqqthsg3.ci.cms.va.gov/pittsburgh-health-care/locations/pittsburgh-va-medical-center-university-drive/gastroenterology

   • Validate that under "Recent changes" you see 1 entry at the top from CMS Migrator indicating the node was updated by an "Automated move ..."
   • Click the edit tab and Validate that each of the two "Service Locations" have the same "Appointment phone" that (numbers, type and label) that is found under the "Scheduling" section.
   • Click the revision tab and validate the revision log is there as well and that there is only one of them.
   • Visit the /admin/content/audit/service-locations-detailed?title=Gastroenterology&type_op=in&type%5B%5D=health_care_local_health_service&moderation_state_multiple_workflow_filter=All&field_administration_target_id=12
     • Validate old and new apt text match
     • Validate Apt lead-in and Apt custom match
     • validate new and old online scheduling match
     • validate one apt phone became 2(because there are two locations) and they match
     • validate "use facility phone" is off, because a phone was provided.
     • validate walkins: "unspecified" became "Yes by apt only"

3. Custom apt text Visit the filtered audit

   • Validate that for services that have "Old apt leadin text" have matching "New apt custom text"

4. Multiple Apt phone numbers & phone with custom labels: Visit the filtered View, and scroll down to the bottom for "Women Veteran care - Pittsburgh VA Medical Center-University Drive"

   • Validate that both old and new apt phone numbers have two entries
   • Validate that custom labels they have match old and new.

5. Double check that forward revisions were handled correctly by going to https://pr16911-frzioxcuceuh23pjuqcftuoyfqqthsg3.ci.cms.va.gov/node/5567

   • Validate that there are two revisions that were added by this migration
   • Validate that the top most revision is the draft revision.

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