VACMS-14136: Editors should not be able to rename VAMC facility services.

[Becapa]

Description

Relates to #14136.

Testing done

Cypress tests created as well as manual testing

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 user QA Content Editor

1. Edit a VAMC Facility Health Service node (e.g. 'Pharmacy - Orlando VA Medical Center' /node/22635/edit)
   • Expand the Health service and facility basic info section.
   • Verify that the Facility and VAMC system health service dropdowns are disabled.

As an administrator

1. Edit a VAMC Facility Health Service node (you can use the same example as above)
   • Expand the Health service and facility basic info section.
   • Verify that the Facility and VAMC system health service dropdowns are not disabled.
2. Edit a Vet Center - Facility Service node (e.g. Jackson Vet Center - Workshops and classes' /node/44823/edit)
   • Verify that Vet Center and Service name dropdowns are not disabled.

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]

Tested with QA Content Publisher, too.

[omahane]

Chef's kiss. I like how you also brought Vet Center - Facility Service in line with VAMC so that admins can do all the things.