chore: update external-secrets operator maintainer list

[gusfcarvalho]

updating external-secrets operator maintainer list.

LMK if I did this wrong and should do it via another place instead 🙈

external-secrets/external-secrets#6518
external-secrets/external-secrets#5373

Checklist for maintainer updates

Note

Delete this template if you're not changing the CSV file

• You've provided a link to documentation where the project has approved the maintainer changes.
• The maintainer(s) also created or updated their LFX Individual Dashboard profile.
• You've sent an email with the list of email address(es) to cncf-maintainer-changes@cncf.io for invitations to Service Desk and mailing lists. You can just mark this complete if you are only removing people.
• Optional: You've also sent a PR with affiliation updates to cncf/gitdm.

[Copilot]

Pull request overview

Updates the CNCF project-maintainers.csv data to reflect a revised maintainer list for the External Secrets Operator project.

Changes:

• Removes two existing External Secrets Operator maintainers.
• Adds two new External Secrets Operator maintainers (with affiliations and GitHub handles).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[riaankleinhans]

@gusfcarvalho please see the Copilot review and update.
We have moved External Secrets Operator to maintainer access automation with the .project repo.
Please update the maintainers in the maintainers.yam here: https://github.com/external-secrets/.project/blob/main/maintainers.yaml

We will shortly replace this file with an automated version pulling from all the project's .project/maintainers.yaml file

Once the maintainers should also make sure the profile is updated at openprofile.dev and connected to their Github handle. The automation pull their primary email from their openprofile and us that for granting access to services.

[gusfcarvalho]

@riaankleinhans thanks for the reply. They are already interim-maintainers on that file. @alekc is going to staff our booth in Kubecon NA, and one of the steps asked by the scholarship he is trying to get says their name should be on that project-maintainers.csv list.

Which pointed me towards opening this PR, as some names also needed cleanup