Set up scheduled CI to catch breakages more proactively

[gotmax23]

From the meeting:

^info I propose that for now, we start running our CI on a more scheduled basis and setting it up to file an issue if that scheduled job fails. We can continue working with core to find a better solution that would allow us to be more proactive.

This was inspired by https://github.com/ansible/ansible-documentation/issues/1079, the second time a core change has broken docs. As an alternative to https://github.com/ansible/ansible/pull/82405, this will allow us to figure out that something's broken at least a little earlier. Currently, we only find out that CI is broken when someone opens a new PR and CI fails.

[oraNod]

Thanks for creating this issue @gotmax23 I think it's a good idea to catch ci issues outside of PRs. As mentioned during the docs meeting today we should probably go with a daily schedule. I guess we can discuss it in the PR but I was thinking cron: 0 7 * * * so any failures would greet us in the morning and be close to the top of the stack.

[x1101]

I'm happy to take a swing at this next. Go ahead and assign it to me

[samccann]

Go for it @x1101 and thanks!