continuous-integration.yml: use one job to collect the status of all …

[BacLuc]

…jobs in the workflow

That we can use one required status check in the branch protection rules. This allows to:

• Allows review of the settings which jobs should be required. The merge of a pr leads to the new settings being active
• Not having to synchronize the settings of the required status check with the devel branch. This happens automatically because the configuration is checked in.
• Not having to merge/rebase devel into PRs because the names of the jobs changed but the old/new job names are in the required status checks.
  (see Contribution documentation update #4204 (comment))

[carlobeltrame]

This also makes it possible to break the CI on devel whenever we change the required status checks, right? But we can fix it when it happens.

[BacLuc]

This also makes it possible to break the CI on devel whenever we change the required status checks, right? But we can fix it when it happens.

My change improves this, because we don't have to change the branch protection rules anymore.
As long as the required checks pass, the ci passes in devel too

[carlobeltrame]

This also makes it possible to break the CI on devel whenever we change the required status checks, right? But we can fix it when it happens.

My change improves this, because we don't have to change the branch protection rules anymore.
As long as the required checks pass, the ci passes in devel too

I don't think so. Assume we add a new required status check to the workflow on devel. Now any old PRs can fail this newly required status check, but still be merged. But again, this should be rare enough to fix as we go.

[BacLuc]

Let me do it.
I already did this in another Project and IT worked Like a charm