fix(nxls): debounce PassiveDaemonWatcher callback to prevent reconfigure flood

[MaxKless]

Summary

• Adds a 1-second debounce to the PassiveDaemonWatcher listener callback, matching the existing debounce on the old DaemonWatcher path
• Prevents the Nx daemon from flooding the language server with thousands of concurrent reconfigure cycles when it delivers a burst of project graph recomputation notifications

Fixes #3101

Context

The Nx daemon can deliver bursts of project graph recomputation notifications (16k+ observed in the logs attached to #3101). The old DaemonWatcher path (used for Nx < 22.5.0) already wraps its callback with debounce(callback, 1000), but the new PassiveDaemonWatcher path (Nx >= 22.5.0) passes the callback through directly. Each notification triggers a full reconfigure() cycle — and while nxWorkspace() deduplicates the project graph computation, the 16k concurrent reconfigure calls all proceed to re-register watchers and configure schemas simultaneously, freezing the language server.

Test plan

• Verify existing e2e tests pass
• Manually test with a large Nx workspace (Nx >= 22.5.0) — file changes should still trigger workspace refresh, but rapid bursts should coalesce into a single refresh

🤖 Generated with Claude Code

[nx-cloud-snapshot]

View your CI Pipeline Execution ↗ for commit 168e3ae

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e-ci,ty...	✅ Succeeded	9m 42s	View ↗
nx-cloud record -- yarn nx sync:check	✅ Succeeded	8s	View ↗
nx-cloud record -- yarn nx run-many -t ktfmtFormat	✅ Succeeded	5m 29s	View ↗
nx run-many -t ktfmtFormat	✅ Succeeded	5m 25s	View ↗
nx-cloud record -- yarn nx format:check --verbose	✅ Succeeded	5s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-07 10:41:45 UTC

[MaxKless]

duplicate of #3104 (review)