VACMS-16575: Add extra validation to allow for combination of reusable and single page QAs.

[Becapa]

Description

Relates to #16575 .

Testing done

Screenshots

QA steps

As a user with content_admin role

1. Create a new CLP page filling in all of the required fields.
2. Expand the FAQs section and click to Enable this page segment
3. Click to Add Page-Specific Q&A and fill out the required fields (Question/Answer).
4. Click to Add Reusable Q&A Group, then expand the Q&As section within.
5. Click to Add Reusable Q&As
6. Check 10 items in the modal and click to Select Q&As
7. Fill in a Revision log message and hit Save
   • Verify that you get an error message near the Page-Specific Q&A fields that says 'Remove Page-Specific or Reusable Q&As. A maximum of 10 Q&As is allowed.
8. Remove the Reusable Q&A group by clicking the 3 dot dropdown and selecting Remove.
   • Try to save again and verify that you get a different error message near the Q&A fields that says 'Add Page-Specific or Reusable Q&As. A minimum of 3 Q&As is required.'
9. Remove the Page-Specific Q&A group by clicking the 3 dot dropdown and selecting Remove.
   • Try to save again and verify that you get an error at the top of the page that says 'A minimum of 3 Q&As is required when the FAQ page segment is enabled. Disable the FAQs page segment if there are not Q&As to add.
10. Expand the FAQs section and uncheck Enable this page segment.

• Verify that you can now save successfully.

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

[Becapa]

I'm unable to approve the changes, but the QA steps all pass and the code looks good to me.