Fail batch-aborted pipelines with reason

What does this MR do?

We recently rolled out a performance improvement to blocking users, which would cancel any of their running pipelines in bulk. This was part of rapid actionpipeline abuse and we did the simplest thing we could think of then: just cancelling them all in batch.

However, the semantics of the cancel status are actually that this is a user initiated action, which is not true in this case.

As suggested in #324646 (closed) we should use the failed status instead and provide a failure_reason so that it is clear why these pipelines have been canceled. This is implemented in this MR.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Related to #324646 (closed)