Less frequent CI runs

[mbackenkoehler]

Currently, the CI runs once a week. With the upcoming DL_edition update the runs become much heavier. So until we have a more fine-grained checking mechanism, we can probably stretch that to once a month.

[dominiquesydow]

Once a month seems a bit too long for this repo that is being used quite a lot for teaching, in my opinion. Maybe every two weeks? But up to you @AndreaVolkamer.

Whatever you decide, can you please update this in our repo overview accordingly?
https://github.com/volkamerlab/lab_repos_check
Thanks!

---

If the DL talktorials take too long in the CI, can you think of ways to make this work more elegantly during testing (we do have quite a few notebooks where we adapted the code in a way that it will be less heavy during CI runs --- if you point me to the code in question, I can think about it; nothing that needs to be done for the DL release).

[mbackenkoehler]

Talktorial 36, for example, is timed out.

[mbackenkoehler]

Typically, some of the 4 jobs fail, due to online resources not being reachable for whatever reason. In that case you have to re-start the jobs a couple of times. So each time there is a pretty high probability of manual intervention being necessary.

Maybe it is also possible to add a retrial scheme for notebooks that use such resources (T001, T018...)?