Organization-level custom agents not visible in Copilot CLI when no GitHub-hosted repository is in the working directory

### Describe the bug

Organization-level custom agents defined in the agents/ directory of the org's .github-private repository do not appear in gh copilot CLI (via /agent) unless the CLI is launched from a directory that contains a git repository with a GitHub remote belonging to that organization. This works perfectly fine in VS Code.

### Affected version

_No response_

### Steps to reproduce the behavior

1. Define org-level custom agents in /.github-private/agents/.
2. On a machine with no local clones of any GitHub repository in that org, run copilot from any directory.
3. Run /agent — org-level agents are not listed.

### Expected behavior

Org-level agents should be resolved from the authenticated user's organization membership, not from the git remote of the current working directory.

### Additional context

Our organization uses Azure DevOps for source control and only has the .github-private repository on GitHub. As a result, org-level agents are inaccessible in the CLI without maintaining an otherwise unused GitHub repo clone on every developer machine.

首先，在没有 GitHub 仓库或 remote 的目录中复现该问题，然后在 gh copilot CLI 中运行 /agent 命令，并将其与 GitHub 托管的仓库目录进行比较。跟踪 CLI 如何根据已认证用户的组织成员身份解析组织级 agent，并验证组织的 .github-private/agents/ 目录中的 agent 会出现，而不依赖当前的 git remote。

由索引模型根据 Issue 内容生成。