Fix wrong account selected

[alexr00]

Fixes #8789

[Copilot]

Pull request overview

This PR addresses multi-account authentication selection issues (Issue #8789) by ensuring the extension prefers the workspace-selected account when resolving existing auth sessions, and by refreshing repositories/views when auth sessions change so the UI/data stays consistent with the active account.

Changes:

• Add findExistingSession to prefer the workspace-selected account before considering broader-scope sessions (prevents “wrong account wins” when another account has broader scopes).
• Refresh repositories, PR views, issues, and notifications on auth-session changes, and clear relevant user caches when updating repositories.
• Add unit tests covering multi-account session resolution across legacy/default/additional scope sets.

Show a summary per file

File	Description
src/test/github/credentials.test.ts	Adds tests validating preferred-account session resolution and fallback behavior across scope sets.
src/notifications/notificationsProvider.ts	Ensures the notifications auth provider is cleared when no provider is authenticated.
src/issues/stateManager.ts	Adds an auth-change refresh path that clears cached issue data and refreshes (or fires change) based on auth state.
src/github/repositoriesManager.ts	Replaces credential-cache clearing with refreshRepositories() to re-enumerate repositories and clear per-user caches.
src/github/folderRepositoryManager.ts	Adds optional cache-clearing in repo updates and avoids using global-state user caches during forced refreshes.
src/github/credentials.ts	Introduces findExistingSession and updates session-change handling to trigger consumer updates on account/session changes.
src/extension.ts	Hooks auth-session change events to refresh repositories, PR state, tree, issues, and notifications.

Review details

Suppressed comments (1)

src/github/folderRepositoryManager.ts:767

• When clearCache skips global-state and deletes _fetchAssignableUsersPromise, an in-flight promise started before the clear can still resolve later and overwrite _assignableUsers, write global-state caches, and fire _onDidChangeAssignableUsers with stale data. Add an identity check so only the currently-tracked promise writes results back after completion.

		const globalStateAssignableUsers = clearCache ? undefined : await this.getCachedFromGlobalState<IAccount>('assignableUsers');

		if (!this._fetchAssignableUsersPromise) {

• Files reviewed: 7/7 changed files
• Comments generated: 1
• Review effort level: Lite