Add CODEOWNERS team for oqs-demos

[SWilson4]

See open-quantum-safe/oqs-demos#350 and open-quantum-safe/oqs-demos#351. Leaving as draft pending feedback on those issues/PRs.

Unconditionally, changes to config.yaml must

• be approved by 2 members of the OQS TSC
• not violate permissions documented in GOVERNANCE.md files for sub projects where such files exist

The following goals apply to changes to the file config.yaml with exceptions possible, as long as the rationale for the exception is documented by comments in the file:

• all sub projects should be treated identically wrt roles & responsibilities as per the detailed list below
• teams/team designations are to be used wherever possible; using personal GH handles should only be used in team definitions
• Admin changes to the file must be documented by comments as to the rationale of the change

All the following conditions hold for permissions set in config.yaml:

• sub project maintainers have admin rights on the sub projects
• OQS and sub project release managers have maintainer rights on the sub projects but can themselves set/reset branch protection rules limiting write access to sensitive branches
• sub project committers have write rights on all branches of the sub projects but can request branch protection rules limiting this
• sub project contributors (incl. code owners) have write rights on all branches except main on those sub projects
• OQS and sub project triage actors have triage rights on all branches of the sub projects
• OQS maintainers and LF admins have admin rights on the organization (e.g., org-wide secret management) as well as maintenance rights on the team configurations

[clowarden]

Validation succeeded

✅ The proposed configuration changes are valid!

Configuration changes

Directory

• team oqs-demos-codeowners has been added
  • Maintainers
    • baentsch
  • Members
    • ajbozarth
    • bhess
    • pi-314159

---

🔸 Please review the changes detected as they will be applied immediately once this PR is merged 🔸