ci: setup CODEOWNERS file

[richadr]

This PR updates the CODEOWNERS file to ensure that the correct people are assigned as reviewers for PRs.

• If the file did not exist yet, it was created.
• The pattern * was added with suggested approvers - please check and adjust as needed.
• Comments were aligned across all repos - just one reference to the relevant NL Design System documentation page at the top and a note about the order of the patterns.
• Additionally, the CODEOWNERS file itself was updated to protect the file itself.
  For community repos, the relevant -admin team is added as a reviewer.
  kernteam-admin is also added.
  Good to know: if multiple patterns match, the last pattern takes precedence, and that's why the CODEOWNERS file itself is at the bottom.

FAQ

I don't want to be assigned as a reviewer

When this PR is merged, PRs that match the pattern in the CODEOWNERS file will be automatically assigned to the approvers. If this creates too much noise, you can

1. check your notification settings,
2. remove yourself from the CODEOWNERS file (if you are added through a team, you can change the team, or change the pattern to assign individual reviewers)

How do I enforce that a PR has at least one review from the approvers?

Optionally, a branch protection rule can be created to require reviews. This is not done in this PR (needs a Terraform change) so let us know if you want this to be added.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
example	Ready	Preview, Comment	May 20, 2026 12:07pm

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud