[Feature] [Discussion] CODEOWNERS
@fox0430

Reviewing the changes of others, suggested as PRs, is in general a good idea in order to be able to discuss further adjustments, for instance.  There is a configuration file to ensure that every PR, except from certain people, will be reviewed.  This configuration file is named `.github/CODEOWNERS` and controls which files cannot be edited without a following review by the respective owner(s).  This is thus a security feature and applied in the repositories of the official GitHub Actions, for example.  The people maintaining a repository can thereby control which teams need to review what; the owner, for example, might always want to review anything while the documentation team would have a major interest to stay up-to-date regarding the state of the project's manual.

I noticed that in the latest PRs, you always self-requested a review of the changes if you were not the original author.  Configuring CODEOWNERS would hence automatically request a review from you which would save time.  If you would submit a PR to this repository with CODEOWNERS configured somehow, you would not need to self-review your changes.

There are two downsides of CODEOWNERS I would like to mention:
- Depending on the configuration, you might be unable to receive GitHub's YOLO achievement (merging changes without a previous review) for the respective repository due to the intention of CODEOWNERS.
- Depending on the configuration, Dependabot's "Mail Merging" feature might become unavailable.  With "Mail Merging", I mean the possibility to write an email to Dependabot telling it to merge the changes without needing to sign-in on GitHub.  Bors should still work, though (which is also nice way to hide the Dependabot PRs from GitHub's automatic release notes).