sessions - when applying changes, offer action to open

[bpasero]

No description provided.

[Copilot]

Pull request overview

Adds an “Open in VS Code” follow-up action after applying session changes to the parent repository in the Sessions window, improving the workflow from “apply” to “continue working in desktop VS Code”.

Changes:

• Adds an “Open in VS Code” notification action after successful/partial apply-to-parent-repo operations.
• Switches apply result notifications to notificationService.notify(...) to support actions.
• Introduces opener/product service usage to build and open a vscode://file/... URL.

[Copilot]

openFolderAction.run calls openerService.open(...) but doesn't await or return the promise. If the open fails (e.g. protocol handler missing), the rejection can go unobserved and the notification action may appear to succeed. Make run async (or return the promise) and await openerService.open(...).

[Copilot]

The protocol scheme is derived from productService.quality and defaults to 'vscode-insiders' for any other value. This can produce an incorrect protocol in non-standard builds (e.g. code-oss) and duplicates logic that IProductService.urlProtocol already provides. Prefer using productService.urlProtocol for the scheme here.

Suggested change

	const scheme = productService.quality === 'stable'
	? 'vscode'
	: productService.quality === 'exploration'
	? 'vscode-exploration'
	: 'vscode-insiders';
	const scheme = productService.urlProtocol;