Cleanup lockfile / dependencies

[RobinMalfait]

This PR reduces the installed dependencies by cleaning up the pnpm-lock.yaml file.

This also pins @parcel/watcher such that the lockfile is generated properly becauase of the patched dependencies.

This is a follow-up of #19499, but up to date with the latest state of the repo.

Test plan

• Lockfile is simpler. Most dependencies stayed the same, and were published months ago. There are a few cases where we have more recent published dependencies. There are 7 dependencies that were published in the last ~24 hours: node-releases@2.0.46 (10 hours ago), electron-to-chromium@1.5.361 (12 hours ago), semver@7.8.1 (20 hours ago), terser@5.48.0 (20 hours ago), webpack-sources@3.5.0 (5 hours ago), vite@8.0.14 (yesterday). All of these but the terser version used OIDC.
• Socket.dev didn't report any issues with the changed dependencies
• All tests still pass

[greptile-apps]

Confidence Score: 5/5

Safe to merge — the only code change is pinning one dependency to an exact version, and the lockfile cleanup removes stale duplicates without altering any application logic.

The package.json change is a single-character version specifier tweak (^2.5.1 → 2.5.1) motivated by patch-file semantics; the resolved version in the lockfile is unchanged. The rest of the diff is a lockfile regeneration that updates peer-dependency resolution strings and removes redundant entries. No application code, tests, or configuration logic is touched.

No files require special attention.

_{Reviews (1): Last reviewed commit: "re-generate `pnpm-lock.yaml`" | Re-trigger Greptile}

[coderabbitai]

Walkthrough

The pull request updates the @parcel/watcher dependency specification in the Tailwind CSS CLI package configuration. The version constraint was changed from a caret-pinned semver range (^2.5.1) to an exact version pinning (2.5.1). This modification restricts the package to version 2.5.1 specifically rather than allowing patch or minor version upgrades within the 2.x range during dependency resolution.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Cleanup lockfile / dependencies' accurately reflects the main changes: pinning @parcel/watcher and cleaning up the lockfile.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The PR description clearly explains the changes: pinning @parcel/watcher and cleaning up the pnpm-lock.yaml file to reduce dependencies. It includes test plan details and references a prior related PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}