fix: backport device capability tiers for v6.5.0

[huhuanming]

Summary

• Backport CPU and memory capability profiles plus capability-aware Tab preload policies to release/v6.5.0.
• Keep the change hot-update compatible by excluding all Electron main/preload and Desktop API contract changes.
• Make Desktop renderer use the same browser capability inputs as Web: navigator.hardwareConcurrency and navigator.deviceMemory when available.

Intent & Context

PR #12454 targets x and includes changes under apps/desktop/app/libs, which cannot be delivered through the release/v6.5.0 hot-update path. This PR carries the JS capability classification and preload policy to the release branch without requiring a new Desktop binary.

Root Cause

The exact Desktop capability implementation in PR #12454 depends on Electron main/preload bridge changes. Those source changes are outside the hot-update bundle, so merging them into the release hot-update PR would create a native/binary dependency that the installed v6.5.0 Desktop application does not have.

Design Decisions

• Excluded every apps/desktop/** change, Desktop-specific capability override, and Desktop API type change from the backport.
• Relied on the existing Desktop renderer resolution order (.desktop → .web → generic) so the generic browser implementation is selected when no capability .desktop.ts file exists.
• Kept CPU and memory independent, with conservative behavior: unknown memory never enables full Tab preloading.
• Kept capability results cached per JS runtime/context. Native main and bg have separate JS heaps and initialize independently; the Tab preload policy is consumed by main only.

Changes Detail

• Add Android/iOS CPU tier catalogs and native capability profile resolution.
• Add browser CPU/memory classification for Web, Extension, and Desktop renderer.
• Add capability-aware full/light/disabled Tab preload policies and sanitized decision logging.
• Add versioned developer CPU overrides and regression coverage for audited device tiers, unknown memory, caching, and prototype-safe catalog lookups.

Risk Assessment

• Risk Level: Medium
• Affected Platforms: Mobile, Web, Extension, Desktop renderer
• Risk Areas: Device catalog accuracy, conservative fallback behavior, and Tab preload queue selection
• Excluded: Electron main process, preload bridge, Desktop native/API contracts

Test plan

• yarn jest packages/kit/src/routes/Tab/preloadPolicy.native.test.ts packages/kit/src/routes/Tab/preloadPolicy.test.ts packages/kit/src/routes/Tab/preloadPolicyResolver.test.ts packages/shared/src/performance/deviceCpuTierData.test.ts packages/shared/src/performance/deviceCpuTierUtils.test.ts packages/shared/src/performance/devicePerformanceTier.native.test.ts packages/shared/src/performance/devicePerformanceTier.test.ts packages/shared/src/performance/devicePerformanceTierResolver.test.ts --runInBand (8 suites, 49 tests)
• yarn app:web:build
• yarn app:ext:build
• yarn workspace @onekeyhq/desktop build:renderer
• yarn agent:check --profile commit
• Confirm the PR diff contains no apps/desktop/**, capability .desktop.ts, or Desktop API contract changes