VACMS-16522: Move VAMC System pages to restricted_archive workflow

[omahane]

Description

Relates to #16522

Testing done

Manually

Screenshots

Example page (VAMC System VA Police page)

In production

In the PR environment

QA steps

What needs to be checked to prove this works?

• Log in as an admin
• Assign QA Content Publisher to the "VA Boston health care" section
• Assign QA Content Publisher to the "VA Nebraska-Western Iowa health care" section
• Assign test_Cordie.Kuhn13 to the "Content admin" role

Try to archive VAMC System VA Police page as an editor

• Log in as QA Content Publisher
• Go to VA Boston VA Police page
• Confirm that you cannot archive the page

Try to edit an archived node as an editor

• As QA Content Publisher
• Go to the archived Policies page in VA Nebraska-Western Iowa health care
• Confirm that you cannot edit the page

What needs to be checked to prove it didn't break any related things?

Try to archive VAMC System VA Police page as a content admin

• Log in as test_Cordie.Kuhn13
• Go to VA Boston VA Police page
• Confirm that you can archive the page

Try to edit an archived node as an as a content admin

• As test_Cordie.Kuhn13
• Go to the archived Policies page in VA Nebraska-Western Iowa health care
• Confirm that you can edit the page

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

[swirtSJW]

Code looks great and results in QA passing.

Also update hook output is as expected