Prevent review comment controller collisions across repositories

[Copilot]

In multi-root workspaces, checking out a second PR could make comment controls unresponsive for the first PR. Review controllers could share an ID because the repository segment incorrectly repeated the owner.

• Controller identity

  • Qualify IDs by owner, repository, and PR number:

    github-review-${owner}-${repositoryName}-${number}

• Regression coverage

  • Verify same-owner, same-number PRs in different repositories receive distinct, correctly qualified controller IDs.

• Fixes Unable to add comments on diff files in workspaces with more than one PR in review #8861

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Fixes a multi-root workspace regression where review comment “+” controls could become unresponsive because multiple vscode.comments controllers were created with colliding IDs across different repositories.

Changes:

• Corrects ReviewCommentController ID construction to include owner, repositoryName, and PR number (instead of repeating owner twice).
• Adds a regression test ensuring controllers for same-owner/same-number PRs in different repos produce distinct IDs.

Show a summary per file

File	Description
src/view/reviewCommentController.ts	Fixes controller ID composition to prevent cross-repo collisions in multi-root workspaces.
src/test/view/reviewCommentController.test.ts	Adds coverage asserting controller IDs are correctly qualified and unique across repos.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Low