oauth-apiserver: add OTE serial test jobs to master and release-4.22

[wangke19]

Summary

Add two optional OTE (OpenShift Tests Extension) presubmit jobs for the oauth-apiserver master and release-4.22 branches, modeled after the service-ca-operator OTE jobs:

• e2e-aws-component-serial-ote: runs the openshift/oauth-apiserver/component/serial test suite
• e2e-aws-component-serial-disruptive-ote: runs the openshift/oauth-apiserver/component/serial-disruptive test suite

Both jobs are marked optional: true and use the ipi-aws workflow with openshift-e2e-test ref.

Test plan

• Verify /test e2e-aws-component-serial-ote triggers correctly on an oauth-apiserver PR
• Verify /test e2e-aws-component-serial-disruptive-ote triggers correctly on an oauth-apiserver PR

Replaces #76660 (rebased onto current upstream/main to fix merge conflict in release-4.22-presubmits.yaml).

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wangke19
Once this PR has been reviewed and has the lgtm label, please assign benluddy 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/config/openshift/oauth-apiserver/OWNERS
• ci-operator/jobs/openshift/oauth-apiserver/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-robot]

[REHEARSALNOTIFIER]
@wangke19: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

PR needs rebase.

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]

@wangke19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/core-valid	1ac89f3	link	true	/test core-valid
ci/prow/yamllint	1ac89f3	link	true	/test yamllint
ci/prow/prow-config-semantics	1ac89f3	link	true	/test prow-config-semantics
ci/prow/config	1ac89f3	link	true	/test config
ci/prow/prow-config-filenames	1ac89f3	link	true	/test prow-config-filenames
ci/prow/ci-operator-config	1ac89f3	link	true	/test ci-operator-config
ci/prow/ordered-prow-config	1ac89f3	link	true	/test ordered-prow-config
ci/prow/owners	1ac89f3	link	true	/test owners
ci/prow/openshift-image-mirror-mappings	1ac89f3	link	true	/test openshift-image-mirror-mappings
ci/prow/release-controller-config	1ac89f3	link	true	/test release-controller-config
ci/prow/check-gh-automation	1ac89f3	link	true	/test check-gh-automation
ci/prow/ci-operator-config-metadata	1ac89f3	link	true	/test ci-operator-config-metadata
ci/prow/generated-config	1ac89f3	link	true	/test generated-config
ci/prow/ci-operator-registry	1ac89f3	link	true	/test ci-operator-registry

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.