Change codeowners for enterprise-search

[tutelaris]

Description

As an initiative to rename teams in the Search org from ent-search-* to search-*, it's required to change the code owners here.

This PR is dedicated to changing the codeowners file.

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @tutelaris? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[tutelaris]

@elastic/ingest-eng-prod, can you please add @elastic/ent-search-application team to the repo?

[kderusso]

@tutelaris - Do we want to use @elastic/ent-search-application or should we migrate to some of the newer groups, e.g. @elastic/search-relevance , @elastic/search-experiences , @elastic/search-extract-and-transform , and @elastic/search-inference-team ? Alternately should we consider renaming to something like @elastic/search-team?

[rowlandgeoff]

@elastic/ingest-eng-prod, can you please add @elastic/ent-search-application team to the repo?

@tutelaris Done. elastic/ent-search-application team now have write access. Shall I remove access for elastic/ent-search-application-backend? (Probably after you merge?) Or... is this going to change again based on Kathleen's comment?

[tutelaris]

@tutelaris - Do we want to use @elastic/ent-search-application or should we migrate to some of the newer groups, e.g. @elastic/search-relevance , @elastic/search-experiences , @elastic/search-extract-and-transform , and @elastic/search-inference-team ? Alternately should we consider renaming to something like @elastic/search-team?

We decided to keep the @elastic/ent-search-application team to match with @app-search-team team in Slack

[tutelaris]

@elastic/ingest-eng-prod, can you please add @elastic/ent-search-application team to the repo?

@tutelaris Done. elastic/ent-search-application team now have write access. Shall I remove access for elastic/ent-search-application-backend? (Probably after you merge?) Or... is this going to change again based on Kathleen's comment?

Thank you!
No, you can remove the backend team.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[tutelaris]

Hey @rowlandgeoff , can you please re-review this PR? Thank you!

[rowlandgeoff]

Looks good. I have removed access for the ent-search-application-backend team.