[release-4.18] OCPBUGS-56133: OWNERS: update owners file with current MCO team members

[isabella-janssen]

Closes: OCPBUGS-56133

- What I did
This is a manual backport of #5040 since the automated cherry-pick failed. This updates the OWNERS file to be up to date with the current members of the MCO team.

- How to verify it
N/A

- Description for the changelog
OWNERS: update owners file with current MCO team members

[openshift-ci-robot]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-56133, which is invalid:

• expected dependent Jira Issue OCPBUGS-56038 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
• expected dependent Jira Issue OCPBUGS-56038 to target a version in 4.19.0, but it targets "4.19.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Closes: OCPBUGS-56133

- What I did
This is a manual backport of #5040 since the automated cherry-pick failed. This updates the OWNERS file to be up to date with the current members of the MCO team.

- How to verify it
N/A

- Description for the changelog
OWNERS: update owners file with current MCO team members

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]

@isabella-janssen: 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.

[djoshy]

/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, isabella-janssen

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 [djoshy]

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

[isabella-janssen]

/hold

I thought the backport-risk-assessed label was controlled by the approvers in the OWNERS file, but it does not look like it is. So, I'll wait to backport this as it may not be needed. Relevant Slack thread: https://redhat-internal.slack.com/archives/GH7G2MANS/p1747233059506079

[ptalgulk01]

/label cherry-pick-approved