cleanup emeritus_reviewers and emeritus_maintainers from OWNERS files across kubernetes orgs

[dims]

Describe the issue

Following up from #6333 (comment) and #6333 (comment)

We need to cleanup https://cs.k8s.io/?q=emeritus_reviewers&i=nope&files=OWNERS*&excludeFiles=&repos= and https://cs.k8s.io/?q=emeritus_maintainers&i=nope&files=OWNERS*&excludeFiles=&repos= looks like we need to clean them all up

Original discussion in #3627 (comment)

Also see https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md#owners for the list of official fields

Why are we solving this issue?

• We need the OWNERS file to have the correct structure so it is parsable by tools

To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?

• Yes, click on the url(s), checkout the repositories which have emeritus_reviewers or emeritus_maintainers in their OWNERS files, submit a patch that removes these sections

Does this issue have zero to low barrier of entry?

• Yes.

How can the assignee reach out to you for help?

• Yes. on sig-contribex

[dims]

cc @mrbobbytables

[dims]

/sig contributor-experience

[dims]

/good-first-issue

[k8s-ci-robot]

@dims:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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/test-infra repository.

[Garima-Negi]

/assign

[dims]

@Garima-Negi found more problematic repositories / files:

https://cs.k8s.io/?q=%5E(emeritus%7Cemeritus-approvers%7Cemeritus_approver%7Cemeritus_maintainers%7Cemeritus_reviewer%7Cemeritus_reviewers%7Cowners)%3A&i=nope&files=OWNERS*&excludeFiles=&repos=

[dims]

So the idea here is to open a PR in each repository to remove the section with the wrong key namely:

emeritus
emeritus-approvers
emeritus_approver
emeritus_maintainers
emeritus_reviewer
emeritus_reviewers
owners

When the reviewers ask we point them to this issue and say that the allowed keys are one of those mentioned here:
https://github.com/kubernetes/test-infra/blob/eb87a9362476e00852ac398a2b6417d1f01d4b48/prow/repoowners/repoowners.go#L57-L60

or emeritus_approvers (per conversation in #3627 (comment))

ping me on slack or here if there are any push backs.

Also if someone else can help you, please carve out which repositories you each will tackle as there are a bunch of them.

[dims]

Oh! sorry if you see emeritus-approvers or emeritus_approver you can change it to emeritus_approvers anything else you can delete and follow what the reviewers guidance if they would like the names in another section.