chore(deps): refresh frontend patches

[saagpatel]

Summary

• update Vite to 8.1.4
• update the Tailwind Vite plugin to 4.3.2
• update Prettier to 3.9.5
• regenerate one internally consistent npm lockfile for the compatible patch set

This replaces the split Dependabot PRs #41, #43, and #44, whose independently generated lockfiles fail npm ci. The lint-staged 17 and TypeScript 7 major updates remain separate.

Verification

• npm ci
• npm run verify:required:frontend
• DESKTOP_PET_STRICT_RUST=1 npm run test:smoke
• DESKTOP_PET_STRICT_RUST=1 npm run verify:required:tauri

Lockfile rationale

The split Dependabot branches produced npm lockfiles that failed npm ci. This PR regenerates the combined compatible patch set with Node 22 and npm 10, matching the GitHub Actions runtime, and was verified with a clean npm ci.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4d46525052

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore the nested parser entry for clean installs

After this hunk removes node_modules/git-raw-commits/node_modules/conventional-commits-parser, a clean install is no longer reproducible: running npm ci on this commit fails with Missing: conventional-commits-parser@ from lock file. The top-level conventional-commits-parser@7.0.1 does not satisfy @conventional-changelog/git-client's optional peer range ^6.4.0, so the nested 6.4.0 lock entry that used to appear here is still required for CI and fresh checkouts.

Useful? React with 👍 / 👎.