ci: assign benchmarks/ to engine codeowners

[ramakrishnap-nv]

Summary

• Route benchmarks/ reviews to @nvidia/cuopt-engine-codeowners alongside cpp/, since benchmarks directly exercise solver internals and performance.

Test plan

• Confirm GitHub picks up the new CODEOWNERS rule by checking that a PR touching benchmarks/ auto-requests review from the engine team.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 30acf41e-61fd-418f-82a8-8740f2728523

📥 Commits

Reviewing files that changed from the base of the PR and between 2505189 and c35078d.

📒 Files selected for processing (1)

• .github/CODEOWNERS

---

📝 Walkthrough

Walkthrough

Adds code ownership assignment for the benchmarks/ directory by designating a specific team as the code owner, without modifying any other existing ownership rules.

Changes

Cohort / File(s)	Summary
Code Ownership Configuration .github/CODEOWNERS	Added ownership coverage for benchmarks/ directory path.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: assigning the benchmarks/ directory to engine codeowners in the CI configuration.
Description check	✅ Passed	The description is directly related to the changeset, providing clear rationale for why benchmarks should be reviewed by the engine team and outlining a test plan.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codeowners-benchmarks-engine

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ramakrishnap-nv]

/merge