Add Python-wide code ownership

[Eduard van Valkenburg (eavanvalkenburg)]

Motivation & Context

Ensure Python ownership is consistent across the repository so @eavanvalkenburg is requested for reviews throughout the Python codebase, including paths with package-specific overrides.

Description & Review Guide

• What are the major changes? Added @eavanvalkenburg to the five Python-specific CODEOWNERS rules that previously overrode the broader /python rule without including that owner.
• What is the impact of these changes? Changes under ag-ui, chatkit, core workflows, declarative, and orchestrations will now include @eavanvalkenburg as a code owner.
• What do you want reviewers to focus on? Confirm that every Python CODEOWNERS pattern now includes @eavanvalkenburg.

Related Issue

N/A — repository ownership maintenance requested directly.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

Pull request overview

Adds consistent Python-wide code ownership for @eavanvalkenburg.

Changes:

• Updates five package-specific ownership rules.
• Ensures all Python CODEOWNERS patterns include the owner.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): e5149148d678
Model: gpt-5.6-sol

Overview

The PR adds an existing core Python owner to the five package-specific rules that previously replaced the broader Python rule without retaining that owner. Existing owners, rule precedence, ordering conventions, and minimum owner counts remain intact, and every Python ownership rule now includes the intended owner. No publishable correctness, compatibility, or security concern was established.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.