Prevent release jobs for same project from executing in parallel

[mkuznyetsov]

Is your task related to a problem? Please describe.

During release of 7.25.0 Che operator, it was discovered that release job was activated twice at the same time (possibly due to some ). This resulted in a conflict, when while 1 job has failed and the other succeeded, they both managed to overwrite things like pushing different images & olm files to Quay, and this making the images digests referenced in CSVs to be inconsistent with actual images on Quay.

Describe the solution you'd like

To avoid this, we should restrict the execution of release workflows to a max of 1 at a time. If the job gets triggered again, it has to be auto cancelled, or ensure it doesn't start until the previous run has finished (similarly to Centos CI flow). Most likely, we should use already existing GitHub action.

Describe alternatives you've considered

Additional context

As the best options found so far are 3rd party GH extensions, we need to contact emo@eclipse.org to find out about CQ process for vetting 3rd party runs-with dependencies.

This item is on old until we hear back from Wayne Beaton about this topic.

[mkuznyetsov]

fkirc/skip-duplicate-actions works for our intended purpose