[9.1] (backport #10103) Update code ownership of core-components.yml

[mergify]

With increased components' movement, the role of core-components.yml is becoming critical. The ingest docs team is not qualified to decide on the content of that file.

This PR suggests adding the PM and EM for these file decisions as exclusive owners of the file. That also means they would be gating components updates and changes in each Collector release.

Case in point: the status of some new receivers in #9344

+CC @mlunadia @AlexanderWert @colleenmcginnis

---

This is an automatic backport of pull request #10103 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 8079da9 has failed:

On branch mergify/bp/9.1/pr-10103
Your branch is up to date with 'origin/9.1'.

You are currently cherry-picking commit 8079da94f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/CODEOWNERS

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/9.1/pr-10103 upstream/mergify/bp/9.1/pr-10103
git merge upstream/9.1
git push upstream mergify/bp/9.1/pr-10103

[mergify]

This pull request has not been merged yet. Could you please review and merge it @theletterf? 🙏