Add timeouts for CI jobs

[cdce8p]

Description

I recently had a job run for 6h just to fail. Usually they all complete in <10min (CI) / <30min (Primer). So anything that is taking longer than that is probably going to fail anyway.

This PR adds timeout-minutes to the individual jobs to abort them after a reasonable amount of time. Usually 2x what they actually need. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes

/CC: @DanielNoord Is 60min enough for Primer jobs? From what I've seen an individual one usually takes 20min.

[DanielNoord]

60 minutes is more than enough! I would even consider setting it to 45 or 50, that's more than twice they usually take.

[cdce8p]

60 minutes is more than enough! I would even consider setting it to 45 or 50, that's more than twice they usually take.

👍🏻 We can leave some headroom. It's still much better than the default 6h timeout. Usually those are issues with Github Actions anyway.

[coveralls]

Pull Request Test Coverage Report for Build 1774619958

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.878%

---

Totals
Change from base Build 1772737787:	0.0%
Covered Lines:	14767
Relevant Lines:	15730

---

💛 - Coveralls

[Pierre-Sassoulas]

Great catch @cdce8p ! Should we change to 45mn before merging ?

[cdce8p]

Should we change to 45mn before merging ?

Don't think that's necessary. The primer tests are somewhat separate from the rest already. 1h also isn't that long. Still an improvement over 6h though.