GeezerVison

As a half-workaround to GHA job hangs, this sets an explicit timeout on every job, meaning that it can be restarted after a sane period, rather than the default 6 hour (360 minute) allowance. This has a marginal benefit of freeing up CI resource quicker on such hangs, as we fail far sooner.

I've also standardised job names to use hyphens instead of the current mix of underscores and dashes, and made the order of inputs more consistent in a couple of cases.

Most notably, this means that if the required 'Check whether the needed jobs succeeded or failed' job hangs/fails, it can be restarted in 5 minutes, rather than pushing an empty commit or closing/reopening and triggering the full test suite again.

A

See also:

• gh-103180: Add CI timeouts to all GitHub Actions jobs #103437
• Add a timeout to CI builds #103180

• Issue: Add a timeout to CI builds #103180