Add StepOutOfMemory as reason for BuildRun failure

[SaschaSchwarze0]

Changes

When a BuildRun Pod fails because of too much ephemeral storage usage and is therefore evicted, then we expose this nicely in the BuildRun status as the condition reason is set to PodEvicted. In case a container went out of memory, we did not expose that at all in the BuildRun status while it is quite obvious in the TaskRun and Pod status who print the step/container status.

I am therefore proposing here to introduce the BuildRun failure reason StepOutOfMemory.

Submitter Checklist

• [x] Includes tests if functionality changed/was added
• [x] Includes docs if changes are user-facing
• [x] Set a kind label on this PR
• [x] Release notes block has been filled in, or marked NONE

Release Notes

You can now easily determine that your BuildRun failed because a step went out of memory as the reason is now set to StepOutOfMemory

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/shipwright-io/build/blob/main/OWNERS)~~ [qu1queee] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[qu1queee]

/lgtm