Align TestUtil.findCliPath() lookup order with review feedback

[Copilot]

---

Before the change?

• findCliPath() prioritized PATH before COPILOT_CLI_PATH, and the method/docs drift noted in review comment r3284484448 required correction.

After the change?

• Lookup-order alignment
  • findCliPath() now checks COPILOT_CLI_PATH first, then PATH lookup, then parent-directory fallback.
• Javadoc alignment
  • Updated the “Resolution order” section to exactly match runtime behavior.
• Resulting code path

  String envPath = System.getenv("COPILOT_CLI_PATH");
  if (envPath != null && !envPath.isEmpty()) {
      return envPath;
  }
  
  String copilotInPath = findCopilotInPath();
  if (copilotInPath != null) {
      return copilotInPath;
  }

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• mvn spotless:apply has been run to format the code
• mvn clean verify passes locally

Does this introduce a breaking change?

• Yes
• No

---

[Copilot]

Pull request overview

Aligns TestUtil.findCliPath() (used by test suites that need a Copilot CLI) with prior review feedback by making the runtime lookup order match the documented “Resolution order”, prioritizing explicit configuration via COPILOT_CLI_PATH.

Changes:

• Updated findCliPath() to check COPILOT_CLI_PATH first, then PATH lookup, then parent-directory fallback.
• Updated the Javadoc “Resolution order” list to match the implemented behavior.

Show a summary per file

File	Description
src/test/java/com/github/copilot/sdk/TestUtil.java	Reorders CLI path resolution to prefer COPILOT_CLI_PATH and updates Javadoc to match.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 0