VACMS-17956: Add virtual support to VAMC health services push to Lighthouse

[omahane]

Description

Relates to #17956 Note: also rebases integration branch from with main changes

Testing done

Manually

Screenshots

QA steps

• [x] Run the migration to confirm that the service migration:
• [ ] Confirm that the migrated content looks as expected.

Set up QA Content Publisher

• [x] As an admin, add the following roles to QA Content Publisher
  • [x] Content creator - VAMC
  • [x] Content publisher
• [x] Add the following sections to QA Content Publisher
  • [x] VA Pittsburgh health care

Edit services

• [x] As QA Content Publisher edit Orthopedics - H. John Heinz III Department of Veterans Affairs Medical Center.
• [x] In the Virtual support for the first Service location, choose "No"
• [x] Add another Service Location to the service.
• [x] In the Virtual support for service location, choose "Yes, by appointment only"
• [x] Add another Service Location to the service.
• [x] In the Virtual support for service location, choose "Yes, Veterans can call at their convenience"
• [x] Save the service
• [x] Edit Women Veteran care - H. John Heinz III Department of Veterans Affairs Medical Center.
• [x] In the Virtual support for service location, choose "Virtual visits may be available."
• [x] Save the service

Verify the queue

• [x] As an admin check the Post API Queue
• [x] Confirm that three virtual support options are in the JSON for Orthopedics - H. John Heinz III Department of Veterans Affairs Medical Center.
• [x] Confirm that one virtual support option is in the JSON for Women Veteran care - H. John Heinz III Department of Veterans Affairs Medical Center.

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
• [x] Facilities
• [ ] User support
• [ ] Accelerated Publishing

[github-actions[bot]]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• [ ] pinned all affected GitHub Actions at a specific commit by SHA?
• [ ] reviewed the source code of the action at the commit you are pinning?
• [ ] confirmed that no GitHub security measures are being bypassed?
• [ ] checked for any injection of user content into protected contexts?
• [ ] reviewed Security hardening for GitHub Actions?
• [ ] reviewed GitHub Workflows?

[omahane]

Adam and I tested pushing services and making sure they can still be processed correctly by Lighthouse. We were able to validate that the process is working correctly after this additional field, which they just ignore for now. Lighthouse will make a follow-up ticket to process the new virtual_support field. I think that means merging this PR but keeping the parent ticket live until we and Lighthouse can test and verify the new field.