Delete hidden VAMC facility service fields (fast follow)

[swirtSJW]

User Story or Problem Statement

AFTER the migration has been run on prod and AFTER the FE has switched to using the new Service Location fields
AND has removed the old fields from the GraphQL query, THEN the fields need to have their table cleared and fields removed from config.

Acceptance Criteria

• [ ] Validate that the fields listed below are final set of fields to be removed
• [ ] FE confirms none of the fields being removed appear in the GraphQL query(s) for VAMC Facility Service.
• Field data in tables is cleared out via hook_update_n in va_gov_vamc for the following fields. (see va_gov_backend_update_8009() for an example of the code.)
  • [ ] field_hservice_appt_intro_select
  • [ ] field_hservice_appt_leadin
  • [ ] field_online_scheduling_availabl
  • [ ] field_walk_ins_accepted
  • [-] ~field_phone_numbers_paragraph~ This field is also used on vamc_system_va_police so it can not be cleared out.
• Fields are removed from health_care_local_health_service config
  • [ ] field_hservice_appt_intro_select
  • [ ] field_hservice_appt_leadin
  • [ ] field_online_scheduling_availabl
  • [ ] field_walk_ins_accepted
  • [ ] field_phone_numbers_paragraph
• [ ] Consider using https://prod.cms.va.gov/admin/config/system/delete-orphans after this deploys, in order clear out the orphaned paragraphs field_phone_numbers_paragraph - The warning on the page is scary. We have validated previously that this works, but it is worth trying this on a tugboat environment and doing a content release to make sure nothing blows up.
• [ ] Verify Lighthouse push to ensure these fields are not present

[davidmpickett]

@omahane When you have a chance can you take a look at this ticket for prefining and getting an estimate on this?

[davidmpickett]

Since Service Location Launch won't happen until late S3, this is likely S4 at soonest.

[jilladams]

Moving to Ready in prep for Sprint 4, when we should be able to kill tech debt around SL.