*: update prow OWNERS_ALIASES file

[wuhuizuo]

What problem does this PR solve?

Issue Number: ref #46911

Problem Summary:

What changed and how does it work?

Reverts #54174

Although the code owners of a directory do not conflict with the community member mechanism of the repository, the exit mechanism of the code owners of the directory still needs to be determined(ref: https://internals.tidb.io/t/topic/877
).

Only the repository "/OWNERS" file will be synchronized with the member list in pingcap/community, in which members can participate in the review of the entire repository. However, for subdirectories configured with the "OWNERS" file, the code owners of the directory are needed to determine whether they can be merged.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @wuhuizuo. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[Benjamin2037]

LGTM

[Benjamin2037]

/hold

[Benjamin2037]

/hold

[Benjamin2037]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, ywqzzy

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 [Benjamin2037,ywqzzy]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-06-25 05:19:28.107214224 +0000 UTC m=+696894.592703054: ☑️ agreed by Benjamin2037.
• 2024-06-27 03:45:35.370667618 +0000 UTC m=+864061.856156450: ☑️ agreed by ywqzzy.