Create CI job for allowed-to-fail docs tests
Problem to solve
The technical writing team has regularly scheduled tasks they must perform, and some level of automation of these tasks would be helpful.
cc to @eread, @marcel.amirault, and @axil thanks to recent discussions. I'll link issues as I find them.
Further details
- These tasks tw-monthly-tasks.md are not mission-critical enough to run on every merge request.
- From discussing with @axil, we could consider adding a job only to the less-frequent merge requests that push new documentation content to the website. (Every 4 hours, I think.)
- These jobs could be allowed to fail. While the TWs want this information easily available, they generally involve cleanup invisible to the end user and shouldn't impede docs publishing.