Sessions - fix all changes rendering

[lszomoru]

No description provided.

[Copilot]

Pull request overview

Adjusts the Agent Sessions Changes view rendering logic to better support “All Changes” and “Last Turn” diff-based views (aimed at fixing rendering glitches/incorrect refresh).

Changes:

• Updates repository resolution to open a git repository using workingDirectory (and now fallback to uri).
• Introduces an allChangesObs observable (diff between first/last checkpoint refs) alongside the existing “last turn” diff.
• Reworks loading/progress gating and entry combination based on the selected ChangesVersionMode.

Comments suppressed due to low confidence (1)

src/vs/sessions/contrib/changes/browser/changesView.ts:341

• workingDirectory now falls back to activeSessionRepository?.uri and is passed to gitService.openRepository(...). For some session providers the repo uri can be non-local/read-only (e.g. vscode-agent-host), which other sessions components explicitly treat as unsupported. Add a scheme guard (at least for AGENT_HOST_SCHEME, and likely require file when appropriate) before calling openRepository, otherwise this can trigger failed repo opens / stuck loading in the Changes view.

			const activeSessionRepository = activeSessionRepositoryObs.read(reader);
			const workingDirectory = activeSessionRepository?.workingDirectory ?? activeSessionRepository?.uri;
			if (!workingDirectory) {
				return constObservable(undefined);
			}

			return new ObservablePromise(this.gitService.openRepository(workingDirectory)).resolvedValue;

[rajoonrohi-star]

@