Retrying pipeline with protected actions ignores these actions
Since !10494 (merged), where we introduced protected actions, we consider some jobs as protected. These jobs can be updated only by users who have ability to write to protected branch that job is assigned to.
This means that it is not possible to trigger, but also retry these jobs for some users.
Currently we just ignore these actions and do not make it possible to execute again if someone retried failed / canceled jobs in the pipeline.
What would be the best approach to handle this situation? Should we "actionize" the failed protected action again (make it possible to trigger it again) or just ignore it? Should we make it impossible to retry failed / canceled jobs in the pipeline in that case?