Make `retry`, `cancel` and `delete` action available in pipeline GraphQL schema

In the pipeline header, we used to rely on the paths returned by the BE to determine if we could retry, cancel or delete a pipeline. However with the graphQL change, the paths are always available as we build them in the models. Also, when we have mutations, we won't have the paths at all, so we need the API to tell the FE which actions are available. I either propose each action having its own name in the query (canRetry, canCancel, canDelete) or having an object like pipelineActions with each key being one of the available action (retry, cancel and delete) which a boolean value to know if they are available.