Backend maintainer review noise

Burak Yigit Kaya prefers minimizing backend-maintainer review requests. Chose one focused PR for tightly coupled dependency-graph changes over separate PRs because splitting causes sequencing conflicts and repeated reviews; unrelated changes must remain separate. Remove automatic code-owner requests when the change does not meaningfully alter backend behavior, and explain why backend review is unnecessary.