chore: migrate CODEOWNERS to new component team (26Q2)

[yehzu]

Auto-generated CODEOWNERS migration for 26Q2 team reorganization.

Replaces legacy scrum team references with the new component team assignment, or adds a catch-all if none existed.

See the org-level migration plan for full context.

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

Base Score 5 × ESF 0.1x = 0.5, floored to minimum of 1

Category	Score	Factors
🔭 Scope	2/20	Single CODEOWNERS file, pure configuration, no subsystems or logic touched
🏗️ Architecture	0/20	No architectural impact; GitHub metadata file only
⚙️ Implementation	1/20	Trivial text edit: consolidating two lines into one, replacing one team handle
⚠️ Risk	1/20	Minimal risk; changes code review notification targets only; easily reversible
✅ Quality	1/15	No tests applicable; change is self-explanatory; no documentation needed
🔒 Perf / Security	0/5	No performance or security considerations for CODEOWNERS change

_{Scored by GitVelocity · How are scores calculated?}