feat(codeowners): Initial CODEOWNERS setup

[lucasssvaz]

This pull request introduces a new CODEOWNERS file to the repository, specifying ownership rules for different parts of the ESP32 Arduino Core project. The file ensures that review requests are directed to the appropriate developers based on the file or directory being modified.

Other libraries and files can be added with time. This is only the initial setup.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "fix(codeowners): Add teams": summary looks too short Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

👋 Hello lucasssvaz, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against d9444a7

[lucasssvaz]

@me-no-dev @SuGlider @P-R-O-C-H-Y @pedrominatel PTAL and see if you would like to change/add/remove something.

@rftafas @igrr @Parsaabasi Would you like to be code owners of any specific files ?

[pedrominatel]

Thanks @lucasssvaz, I agree.

[igrr]

I'd suggest adding espressif/admins here, just in case.

[lucasssvaz]

Apparently it needs to be public to be a code owner:

Unknown owner on line 70: make sure the team @espressif/admins exists, is publicly visible, and has write access to the repository 

[igrr]

and optionally espressif/ci here, just in case some workflow has to be updated due to a security issue

[lucasssvaz]

We change our CI files quite frequently. Wouldn't this spam the CI team with review notifications? I have never used CODEOWNERS before so I don't know. The idea is to enable the branch protection rule to require codeowners review and AFAIK this automatically requests the review of all owners.