VACMS-17177: Shows descriptions for vet center services on node view/edit

[Becapa]

Description

Relates to #17177.

Testing done

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 the QA Vet Center Editor user

1. Edit a vet center facility service node (i.e. /node/36809/edit)
   • Validate that a 'General service description' field is visible, but not editable, making note of text in the 'Service description:'.
2. Then click on the view tab for that node.
   • Validate that below the service name it shows the same content from the 'Service description:' from the previous step.
3. Then edit the Vet Center itself (for the above example: /node/3771/edit)
   • Under the 'Services' section find the service from above (i.e. 'Whole health') and click 'Edit'
   • Validate that the 'General service description' is still visible.

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 very clean and easy to read.

I had one very minor suggestion.

[omahane]

Question (for my own edification): Why does this need to be called via reference?

[Becapa]

I'm pretty sure that the reason for this is because we are making changes to the build. If we didn't call it by reference, then we'd just be getting a copy of the build and any changes we make to it below (line 178) wouldn't be reflected in the actual build.

[omahane]

Makes sense.

[omahane]

Ready to go! Nice work.