[WIP] Fix GitHub search tool returning zero matching issues

[Copilot]

• Trace explicit-repository search resolution and paging behavior
• Add a focused regression test for searching a non-workspace repository
• Apply the smallest production fix to search the resolved repository
• Run targeted tests, compile, lint, and hygiene checks
• Scan changed files and run final code/security validation

• Fixes GitHub search tool returns zero matching GitHub Issues despite there being many #8930

[azure-pipelines]

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

[Alex Ross (alexr00)]

Copilot can you give an explanation for the change?

[Copilot]

Copilot can you give an explanation for the change?

Previously, the tool resolved the explicit owner/repo but then called FolderRepositoryManager.getIssues(), whose paging logic only searches active workspace remotes. A requested non-workspace repository was therefore filtered out and could produce zero results.

The change queries the resolved GitHubRepository directly and makes the structured repository input authoritative. It also normalizes any existing repo: qualifier and appends the explicit qualifier outside the Boolean expression, so every branch of the query—and the confirmation link—is scoped to the requested repository. The regression test verifies this path and confirms the workspace-wide search is not used.