provideDocumentSemanticTokens is called on all modified documents after a find/replace leading to the OS freezing

[sean-mcmanus]

Does this issue occur when all extensions are disabled?: Yes (but the repro requires an extension that implements semantic tokens)

• VS Code Version: Version: 1.76.2 (user setup)
  Commit: ee2b180
  Date: 2023-03-14T17:55:54.936Z
  Electron: 19.1.11
  Chromium: 102.0.5005.196
  Node.js: 16.14.2
  V8: 10.2.154.26-electron.0
  OS: Windows_NT x64 10.0.22621
  Sandboxed: No
  and
  Version: 1.77.0-insider (user setup)
  Commit: b9226e1
  Date: 2023-03-24T18:57:27.096Z
  Electron: 19.1.11
  Chromium: 102.0.5005.196
  Node.js: 16.14.2
  V8: 10.2.154.26-electron.0
  OS: Windows_NT x64 10.0.22621
  Sandboxed: Yes
• OS Version: Windows 11

Steps to Reproduce:

1. Do a find/replace on unopened file targets with an extension installed that provides semantic document tokens for those target files.

Bug: In addition to the didOpen, which is fine, VS Code is also invoking provideDocumentSemanticToken for the documents, which doesn't seem to make sense since the documents are not visible, which for the C/C++ extension can lead to the OS to freeze (we have a fix for that, see microsoft/vscode-cpptools#10743), but it seems like VS Code shouldn't be invoking provideDocumentSemanticToken in the first place. Our extension implements vscode.DocumentSemanticTokensProvider.

UPDATE: Also, looks like I had

    "files.autoSaveDelay": 1000,
    "files.autoSave": "afterDelay",

not sure if that matters.