Leverage the LSP / Intellisense of a connected IDE (VS Code / Visual Studio)

### Describe the feature or problem you'd like to solve

Setting up local LSP server for Copilot CLI is unnecessary when a connected IDE can serve those operations

### Proposed solution

Manually setting up an LSP server for Copilot CLI to use is non-trivial.

Suggestion: When Copilot CLI is connected to an IDE like VS Code or Visual Studio, LSP tools like go-to-definition, find-references, hover-info, etc could be forwarded to the IDE - leveraging the LSP and Intellisense functionality there.

### Example prompts or workflows

- User opens Copilot CLI on a repository
- User open VS code on the same repository
- See: Agent operations on the repository leverage semantic understanding (via LSP/Intellisense) served by the IDE, rather than grep operations.

### Additional context

_No response_

首先檢查 Copilot CLI 如何連線到 repository，以及它如何與已連線的 VS Code 或 Visual Studio 執行個體通訊。定義 go-to-definition、find-references 和 hover-info 的轉送路徑，然後驗證 CLI 工作流程範例使用的是 IDE 的 LSP 或 Intellisense 結果，而不是以 grep 為基礎的操作。

由索引模型根據 Issue 內容生成。