Remove @kevin940726 and @Mamaduka from e2e test codeowners

[kevin940726]

What?

Remove @kevin940726 from e2e test codeowners.

Why?

Now that the migration is (nearly) done, and most of the contributors are more familiar with writing playwright tests, I don't think I need to be pinged on every PR that touches tests anymore. Also, It's kind of overwhelming and I have less time to help on tests now 😅.

How?

Edit CODEOWNERS.

Testing Instructions

Nothing to test.

Screenshots or screencast

N/A

[kevin940726]

@Mamaduka Do you want to do the same? 😆

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: kevin940726 <kevin940726@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

You're making a good point, and yes, please!

[Mamaduka]

Thank you, @kevin940726!

[github-actions]

Flaky tests detected in b9cfefd.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8373046179
📝 Reported issues:

• [Flaky Test] should multi-select block with text selection and a block without text selection #59579 in /test/e2e/specs/editor/various/multi-block-selection.spec.js

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: [Type] Automated Testing, [Type] Project Management.

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.