Workaround for #28593

**Bug**
TypeScript Server is hanging onto a file in `node_modules/.staging`, causing npm installs to fail. I believe the root cause is that 0d5c9f41 changed vscode logic to always open the `triggerFile` in config diagnostic events.  In this case, TS sends us a trigger file from `.staging` which we then tell the TS Server to open

**Fix**
Disable checking the trigger file

Q data during pty launch delay Fixes: #29184

Implement context menu actions in CompositePart

Fixes #23636: when trim whitespace is not ignored, first diff the lines with trim whitespace ignored and then post-process to add trim whitespace changes

tfs: test nvm in darwin

tfs: darwin, source nvm

tfs: darwin nvm

tfs: make sure darwin nvm works

tfs: darwin nvm

tfs: linux nvm

tfs: test linux nvm

tfs: linux nvm

tfs: nvm for linux and darwin

tfs: fix nvm switch

tfs: windows nvm

tfs: nvm windows

tfs: windows nvm

tfs: windows nvm

tfs: fix windows nvm path

tfs: windows nvm

tfs: windows nvm

tfs: windows nvm

tfs: windows nvm

tfs: windows nvm

tfs: fix windows nvm

tfs: windows nvm

tfs: unify node.sh

tfs: linux, darwin nvm

Add *.props as a recognized file extension for XML