refactor(data): scope async resource consumers

[beruro]

Problem

Shared application loaders could publish late results after project, workspace, session, or browser scope changes. Some polling/countdown work also continued while hidden, and browser diagnostic state could outlive the surface that owned it.

Solution

• Migrate application, project, browser, git, settings, policy, skill, terminal, and sidebar consumers to the scoped async-resource lifecycle introduced by refactor(async): add scoped resource lifecycle #562.
• Fence late results by stable scope identity and suspend eligible polling/countdowns while hidden.
• Preserve copied error stacks and browser diagnostic scopes only for their valid lifecycle.
• Integrate the latest refactor(async): add scoped resource lifecycle #562 base while retaining its newer view isolation, bounded-concurrency, permissions, and selected-repository behavior.
• Keep the latest useGitHubWorkItemsLoadLifecycle implementation from the base because it now owns a more advanced viewer-isolated retention and permission lifecycle than this older sweep; its focused tests still pass.

The updated branch is based on the current #562 head and GitHub reports it mergeable.

Potential risks

• This remains a broad 40-file consumer sweep; an incorrect scope key can still expose stale cross-project data.
• Browser close/unmount, visibility return, and project reactivation are the highest lifecycle-risk paths.
• The GitHub work-items loader no longer changes in this PR because the base implementation superseded that portion of the original sweep. Future lifecycle changes there must preserve viewer/store isolation and bounded concurrency.
• This PR depends on refactor(async): add scoped resource lifecycle #562 and should be merged/retargeted only after refactor(async): add scoped resource lifecycle #562. Rollback is a normal revert after its base lands; no schema, wire, dependency, or persistence migration is involved.

Verification

• ./node_modules/.bin/vitest run src/modules/MainApp/WorkManagement/useGitHubWorkItemsLoadLifecycle.test.ts — PASS, 6 passed / 0 failed.
• ./node_modules/.bin/eslint on the five integration-conflict files — PASS, no errors or warnings.
• ./node_modules/.bin/tsc --noEmit --pretty false — PASS.
• git diff --check — PASS.
• Merge of the updated refactor(async): add scoped resource lifecycle #562 branch — PASS after semantic conflict resolution; final diff remains limited to 40 scoped-lifecycle consumer files.
• Full repository CI is running on the published merge commit.