NO-ISSUE: Add runtime crun to crio for y-2 blueprint

[pmtk]

microshift 4.15 RPM still specifies crio >= 1.25 and doesn't ship its own crun runtime definition for crio. When it gets newest crio (>= 1.29), the test fails because crio exits shortly after startup.
This PR introduces a workaround: explicitly adds missing file to the blueprint.
When 4.15 RPM has its crio version fixed, we can remove the workaround.

[openshift-ci-robot]

@pmtk: This pull request explicitly references no jira issue.

In response to this:

microshift 4.15 RPM still specifies crio >= 1.25 and doesn't ship its own crun runtime definition for crio. When it gets newest crio (>= 1.29), the test fails because crio exits shortly after startup.
This PR introduces a workaround: explicitly adds missing file to the blueprint.
When 4.15 RPM has its crio version fixed, we can remove the workaround.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[pmtk]

/override ci/prow/microshift-metal-tests ci/prow/microshift-metal-tests-arm

Because test we're trying to fix here is using images from cache, it's not taking into consideration change in this PR. We need to merge this, so next night it's rebuilt.

[openshift-ci]

@pmtk: Overrode contexts on behalf of pmtk: ci/prow/microshift-metal-tests, ci/prow/microshift-metal-tests-arm

In response to this:

/override ci/prow/microshift-metal-tests ci/prow/microshift-metal-tests-arm

Because test we're trying to fix here is using images from cache, it's not taking into consideration change in this PR. We need to merge this, so next night it's rebuilt.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

@pmtk: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[pacevedom]

/lgtm
Will open a ticket to remember this.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom, pmtk

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 [pacevedom,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment