fix: clean CI warnings and stabilize tests

[Sun-sunshine06]

Summary\n- clean the remaining lint warnings in main, renderer, and sandbox modules\n- make credential, path resolver, logger, and plugin runtime tests less brittle across platforms and slower CI runs\n- skip directory symlink-specific assertions when the local Windows environment cannot create symlinks\n\n## Verification\n- npm run lint\n- npm run typecheck\n- npm run test:coverage

[hqhq1025]

✅ LGTM — Approve

Lint fixes are correct and don't change behavior. Symlink detection logic (supportsDirectorySymlinks() probe) is sound.

Minor observations (non-blocking)

• plugin-runtime-service.test.ts timeout bump to 15s — the underlying mock-based test shouldn't need this. Worth investigating the root cause separately.
• ChatView.tsx ResizeObserver useEffect has duplicate eslint-disable-next-line suppression
• MessageCard.tsx useMemo on contentBlocks busts every render during streaming (rawContent changes each time), providing no real optimization benefit
• Logger getLogContent polling approach is slightly less reliable than the previous stream finish event. Acceptable for now but noted.

[hqhq1025]

This PR has merge conflicts with the current main branch (likely from the recent skills extraResources change in electron-builder.yml and/or the scrypt fix just merged in #81). Please rebase onto main to resolve.

[hqhq1025]

Hi @Sun-sunshine06, thanks for the comprehensive CI cleanup work!

I've cherry-picked the most valuable parts of this PR into main (commit 5206ba1):

Adopted:

• lima-bridge.ts / wsl-bridge.ts: .values() iterator simplification
• dangling-symlink.test.ts: Windows symlink capability detection (supportsDirectorySymlinks())
• path-resolver-containment.test.ts: MountedPath type import replacing as any
• store-encryption.test.ts: vi.doUnmock() fix and formatting

Not adopted (with reasons):

• MessageCard.tsx useMemo — rawContent changes every tick during streaming, so the memo never hits cache (net negative optimization)
• store/index.ts removeSession — the existing destructuring pattern is the correct Zustand immutable update pattern
• logger-context.test.ts — polling approach is less reliable than the current stream finish event method
• useApiConfigState.ts — pure formatting with no functional change, high rebase conflict risk
• App.tsx useEffect deps — empty deps array is intentional (paired with ref guard for mount-once behavior)
• ChatView.tsx useCallback — current useRef(fn).current is a zero-overhead stable reference pattern
• plugin-runtime-service.test.ts type definitions — caused cascading type errors due to PluginCatalogItemV2.catalogSource being a string literal type

Your authorship is preserved via --author on the commit. I'm going to close this PR since the relevant changes are now on main. Thanks again for the contribution! 🙏