Product review of VAMC System Banner Alert proposed path forward

[xiongjaneg]

Description or Additional Context

• Reported defect: If an un-published VAMC System Banner Alert is still linked from the system VAMC System Operating Status, the node will not allow Content Publishers to save their changes.
• Public Websites recently dealt with a similar issue around inline editors. Might be a useful reference.

To Reproduce

Steps to reproduce the behavior:

• Log in on Staging as a Content Publisher and go to your assigned system's VAMC System Operating Status node (i.e. /pittsburgh-health-care/operating-status )
• Create a new VAMC System Banner Alert or select the name of an existing VAMC System Banner Alert. Make sure the alert is published.
• Find the VAMC System Banner Alert via the Content page and un-publish it
• Go back to the VAMC System Operating Status node
• Make sure the un-published VAMC System Banner Alert is still listed within the "System-wide alerts" section of the page.
• Attempt to make other changes to the page.
• You will not be able to save and publish while the un-published Banner Alerts are still linked

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [x] Facilities
• [ ] User support
• [ ] Accelerated Publishing

Acceptance Criteria

• [ ] UX, engineering, and accessibility recommendations are reviewed
• [ ] If CMS Design System review is needed, ticket is created
• [ ] Implementation tickets are created
• [ ] #13543 is updated

[jilladams]

@xiongjaneg

• Drupal SPIKE #15047 = ✅
• CMS implementation #13543 = is ticketed and ready to prioritize
• FE review #15057 = ✅ & Max has a draft PR that can be refreshed & merged when CMS changes are complete

So I think this ticket is the last blocker to getting that ball rolling.

[jilladams]

Also, it would be nice to clean up #1392 and refine which things we are taking on under this project.

[xiongjaneg]

lower in priority than current issues and epics, moving to backlog