Fixes stale single-file scope when re-entering resolve mode

A per-file resolve entry sets `resolveFocusedFilePaths`, but exiting the
mode never cleared it — every other piece of engagement state is reset in
`hideMode` except this one. A later session started from the details
header's Resolve chip (which doesn't pass a scope) then silently reused
the previous session's single-file focus instead of targeting all
conflicted files. Clears the focus on resolve-mode exit, scoped to the
exiting mode so a compose→resolve switch can't wipe a focus the entry
point just set.

Author: ianhattendorf

src/webviews/apps/plus/graph/components/detailsWorkflowController.ts

@@ -646,6 +646,11 @@ export class DetailsWorkflowController implements ReactiveController {
 			this.review.invalidateErrorRecovery();
 		} else if (exitingMode === 'compose') {
 			this.compose.invalidateErrorRecovery();
+		} else if (exitingMode === 'resolve') {
+			// The focused-file scope is an input of the engagement that set it (per-file/multi-select
+			// entry points) — clear it on exit so a later chip-initiated session defaults back to all
+			// conflicted files instead of silently re-scoping to the previous session's file(s).
+			this.actions.state.resolveFocusedFilePaths.set(undefined);
 		}
 		// On repo-switch, the caller (Trigger 1 in hostUpdate) will follow up with the new
 		// repo's selection arriving. Refetching here uses `host.currentSelection()` which is