Parse uri= simplified format for open-issue-webview links

[Copilot]

Issue links emitted by VS Code chat (via microsoft/vscode#320404) use a simplified ?uri=… query, e.g.

vscode-insiders://github.vscode-pull-request-github/open-issue-webview?uri=https://github.com/microsoft/vscode-tools/issues/964

fromOpenIssueWebviewUri only understood the legacy JSON-encoded query and returned undefined, so the URI handler silently dropped the click.

Changes

• src/common/uri.ts – fromOpenIssueWebviewUri now first attempts to parse a uri=https?://github.com/<owner>/<repo>/issues/<n> query parameter (anchored regex rejects extra path segments and non-numeric numbers), then falls back to the legacy JSON format. Mirrors the existing fromOpenOrCheckoutPullRequestWebviewUri shape.
• src/test/common/uri.test.ts – Adds coverage for the new format, http variant, JSON fallback, invalid authority/path/host, non-numeric numbers, and trailing path segments.

[Copilot]

Pull request overview

This PR updates the extension’s URI parsing so that “open issue” links emitted by VS Code chat using the simplified ?uri=… query format are correctly recognized, instead of being silently dropped by the URI handler.

Changes:

• Extend fromOpenIssueWebviewUri to parse the simplified uri=https?://github.com/<owner>/<repo>/issues/<n> query format, with strict URL validation, and fall back to the legacy JSON query format.
• Add unit tests covering the new simplified format, legacy JSON fallback, and multiple invalid-input cases.

Show a summary per file

File	Description
src/common/uri.ts	Adds simplified uri= query parsing for issue-webview links before falling back to legacy JSON parsing.
src/test/common/uri.test.ts	Adds coverage for simplified-format issue URIs and validation/compatibility cases.

Copilot's findings

Comments suppressed due to low confidence (1)

src/common/uri.ts:729

• In the legacy JSON fallback, JSON.parse returns any, so issueNumber might be a string (or other non-integer) even if validateOpenWebviewParams passes. Returning query directly can leak an unexpected type into downstream code that assumes issueNumber: number (e.g. uriHandler.ts passes it as identity.number). Coerce and validate issueNumber as a safe integer before returning, and return a strongly-typed object.

		const query = JSON.parse(uri.query.split('&')[0]);
		if (!validateOpenWebviewParams(query.owner, query.repo, query.issueNumber)) {
			return;
		}
		return query;

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