Exclude specific exported identifiers from auto import suggestions

まだ誰も着手していません。

### 🔍 Search Terms

Exclude named imports

### ✅ Viability Checklist

- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

There are libraries like `@mui/material` that have a number of named imports such, e.g. `createTheme`, `useTheme`, `debounce`, `darken` that can pollute intellisense.

While I don't want to exclude the entire `@mui/material` module, it would be great if I were able to exclude specific named imports so they do not show in the intellisense.

### 📃 Motivating Example

I have my own methods for `useTheme` and `darken` and wish to show my own methods in the intellisense and exclude those from `@mui/material`.

### 💻 Use Cases

1. What do you want to use this for?
I want to be able to exclude specific named imports from modules

2. What shortcomings exist with current approaches?
It requires updates when modules change their named imports

3. What workarounds are you using in the meantime?
None

この issue にはソースファイル、テスト、エントリーポイントのいずれも記載されていません。まず TypeScript の auto-import と IntelliSense の候補実装を見つけ、次にモジュールレベルの除外がどのように設定およびテストされているかを確認してください。ユーザーがモジュール全体を除外せずに、モジュールから選択した名前付きインポートを除外できれば完了です。

索引モデルが issue の本文から書いたものです。