Allow to Override Import Paths For Auto-Import

IDisposable, Emitter and Event are very common types in the VS Code codebase.
Unfortunately, you have to be very careful when importing them through autocomplete.
Even worse, sometimes all the places to import from are suggested except the correct one.

In 99% of cases, we are importing IDisposable from vs/base/common/lifecycle. As you can see here, TypeScripts suggests all places except the right one:

It would be very practical if one could override where to import unresolved symbols from.
E.g.

"typescript.importFromOverrides": {
  "src/vs/editor/**": {
    "IDisposable": "vs/base/common/lifecycle",
    "Event": "vs/base/common/events"
  }
}

Alternatively, TypeScript could figure out where the Symbol has been imported from in adjacent files.
Maybe a disallow-list would also make sense (never import IDisposable from node-pty, or never import anything from vs/workbench/workbench.web.api).

This is now the second codebase where I ran into the permanent problem of importing a common symbol from a wrong module, which makes me believe this is a common problem.
I run into this problem one to ten times per day.

Here is another example:

We never want to import from vscode.
Being able to customize the preferred import would be a huge deal (especially for the quickfix "add all missing imports").

Das gemeldete Verhalten von Auto-Import und Quick-Fix in der VS Code-Codebasis mit Symbolen wie IDisposable, Emitter und Event reproduzieren. Die vorgeschlagenen Module mit den bevorzugten Importpfaden in den Beispielen vergleichen; abgeschlossen bedeutet, dass das angeforderte Verhalten für Importpräferenzen oder Ausschlüsse unterstützt wird und beim Hinzufügen fehlender Importe funktioniert.