Add benchmark-runner step-registry for Prow CI migration

[arpsharm]

Add step redhat-performance-benchmark-runner under ci-operator/step-registry/redhat-performance/benchmark-runner/:

• OWNERS, ref yaml, commands script, ref.metadata.json
• Step runs python3.14 /benchmark_runner/main/main.py using ci/benchmark-runner image
• Approvers/reviewers: arpsharm, paigerube14, ebattat, RobertKrawitz, jeniferh, gqlo

Part of Jenkins to Prow CI migration for PerfCI workloads.

[openshift-ci]

Hi @arpsharm. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: arpsharm
Once this PR has been reviewed and has the lgtm label, please assign pmacik for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/redhat-performance/OWNERS

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

[openshift-ci]

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing /verify-owners in a comment.

• arpsharm
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • ci-operator/step-registry/redhat-performance/benchmark-runner/OWNERS

[paigerube14]

/assign @paigerube14