refactor(data): scope async resource consumers

[beruro]

Problem

Shared application loaders and diagnostics consumers can commit late results after project, workspace, session, or browser scope changes, and some polling/countdown work continues while the window is hidden.

Solution

• Migrate application, project, browser, git, settings, policy, skill, terminal, and sidebar consumers to the scoped lifecycle from refactor(async): add scoped resource lifecycle #562.
• Fence late results on scope changes and suspend eligible polling/countdowns while hidden.
• Preserve copied error stacks and browser diagnostic scopes after close.
• Validation: focused lifecycle tests, TypeScript typecheck, all changed-file ESLint, and diff check against the refactor(async): add scoped resource lifecycle #562 base.

Potential risks

• Depends on refactor(async): add scoped resource lifecycle #562 and must be retargeted to develop only after refactor(async): add scoped resource lifecycle #562 merges.
• This is a systematic consumer sweep across 41 files; missed or incorrectly keyed consumers could still show stale cross-scope data.
• Browser close/unmount and visibility-return paths remain the highest lifecycle-risk areas.