fix(windows): stabilize installer and update handoff smoke

[SunwardL]

Summary

• give the complete Windows installer migration step 120 minutes and its enclosing job 180 minutes in PR, daily, and release workflows
• keep each installer and copied-uninstaller process bounded to 600 seconds with explicit PID/scenario failures
• keep restored manual-upgrade user files at their actual source until the external-drive fixture is staged
• assert all-users outer/inner installer evidence on the diagnostic action that records it
• normalize Win32 CIM process creation time to ISO-8601 before packaged handoff identity verification

Why

Follow-up to #1257. Successive Windows runs exposed independent assumptions in the smoke path: the full migration matrix exceeds 60 minutes, individual clean installs can exceed 300 seconds, rollback restores unknown files to the legacy source, all-users source/UAC evidence is emitted by FallbackCleanup, and Windows PowerShell 5.1 serializes CIM CreationDate as /Date(...)/, which Date.parse() cannot verify.

The workflow remains bounded at every layer. The identity fix also keeps the fail-closed PID-generation checks intact; it only makes the PowerShell timestamp transport unambiguous.

Tests

• npx vitest run src/main/windows-installer-manual-upgrade-smoke.test.ts src/main/windows-installer-migration.test.ts (39 passed)
• npx vitest run src/main/kun-process.ports.test.ts src/main/kun-process-identity.test.ts (20 passed)
• npm run typecheck
• ESLint on all changed TypeScript files
• Windows PowerShell 5.1 parser validation for changed smoke scripts
• parsed all three updated workflows and verified Windows budgets: job 180, migration 120, handoff 20
• npm run check:file-lines
• git diff --check
• configured Windows win-unpacked rebuild
• npm run smoke:packaged-update-handoff -- --resources dist/win-unpacked/resources (4 update paths and 2 fail-closed owner cases passed)
• GitHub run 33617817308 reached the penultimate long migration scenario before the old 60-minute step limit terminated it