VACMS-19077: Aging Content for News Spotlight blocks

[dsasser]

Description

Relates to #19077

Testing done

Automated and manual

Screenshots

Queued Expired/Warned News Spotlight Notifications:

QA steps

Generate Test Content

Expirable content is dependant on the content having changed 14 days ago. In order to ensure we have content to test with, I wrote a script at scripts/content/VACMS-19077-generate-test-content.php that creates 3 blocks: one expired, one in warning, and another that is neither.

• [ ] Open a Terminal
• [ ] Run drush scr scripts/content/VACMS-19077-generate-test-content.php
• [ ] There is no output from the command.

QA Steps

• [x] Open the Expired View
• [x] In the Preview section, ensure you see a block with the description: Expirable Content Test Block:expired
• [x] Open the Warn View
• [x] In the Preview section, ensure you see a block with the description: Expirable Content Test Block:warn
• [x] Wait for mighnight's Cron
• [x] Check that there are two News Spotlight blocks in the Queue with the status of 'Queued' that have the same descriptions. A quick way to search is CMD+F+description from above, eg
• [x] Check the Captured Mail on the Tugboat and ensure you see at lest two emails representing the expected notifications (tbd needs QA step improvement)

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

[github-actions[bot]]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• [ ] pinned all affected GitHub Actions at a specific commit by SHA?
• [ ] reviewed the source code of the action at the commit you are pinning?
• [ ] confirmed that no GitHub security measures are being bypassed?
• [ ] checked for any injection of user content into protected contexts?
• [ ] reviewed Security hardening for GitHub Actions?
• [ ] reviewed GitHub Workflows?