VACMS-17325: Restore missing add buttons

[omahane]

Description

Relates to #17325

Testing done

Manually

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?

Setting up the QA Content Publisher

• Login as an admin
• Go to the QA Content Publisher user
  • Set the role to "Content creator - VAMC" and "Content publisher"
  • Set the Section to "VA Boston health care"

Testing as the editor

Login as QA Content Publisher

• Add a VAMC Facility Health Service

  • Click on the Contact info accordion
  • Confirm that the "Add new phone number" button is present
  • Confirm that the "Add new email address" is present

• Edit a VAMC Facility Health Service

  • Click on the Contact info accordion
  • Confirm that the "Add new phone number" button is present
  • Confirm that the "Add new email address" is present
  • Click on the "Hours" accordion to test that no regression was introduced
  • Change the Monday hours to 8 am to 8 pm
  • Save the node

• Login as an admin

  • Check the Post API Queue
  • Confirm that there's an entry for "Amputation care - West Roxbury VA Medical Center"
  • Do a page search for "monday":"08:00 a.m. to 08:00 p.m."
  • Confirm that you found that string

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

[omahane]

@edmund-dunn It looks like the maintainer has added a fix for a new release that will be out in a couple days. I'm going to text his fix now to make sure it works for us in anticipation of the 1.17.0 release.

[omahane]

I tested the maintainers fix successfully: #17325 (comment)