NO-JIRA: Add OWNERS file to test directory

[cblecker]

What this PR does / why we need it:

Adds an OWNERS file to the test/ directory to establish proper code ownership for the test suite. This is part of efforts to refactor and improve HyperShift's e2e suite.

Which issue(s) this PR fixes:

Contributes to OCPSTRAT-2499

Special notes for your reviewer:

Simple addition of an OWNERS file with no code changes.

Checklist:

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs. (N/A - OWNERS file is self-documenting)
• This change includes unit tests. (N/A - no code changes)

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

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

Details

In response to this:

What this PR does / why we need it:

Adds an OWNERS file to the test/ directory to establish proper code ownership for the test suite. This is part of efforts to refactor and improve HyperShift's e2e suite.

Which issue(s) this PR fixes:

Contributes to OCPSTRAT-2499

Special notes for your reviewer:

Simple addition of an OWNERS file with no code changes.

Checklist:

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs. (N/A - OWNERS file is self-documenting)
• This change includes unit tests. (N/A - no code changes)

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.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cblecker
Once this PR has been reviewed and has the lgtm label, please assign muraee 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:

• OWNERS

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

[cblecker]

/cc @sjenning @csrwng
/verified bypass

[openshift-ci-robot]

@cblecker: The verified label has been added.

Details

In response to this:

/cc @sjenning @csrwng
/verified bypass

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.

[openshift-ci]

@cblecker: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.