Configurable import suggestions to override global types

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section. --> ## Search Terms <!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily --> ## Suggestion In our code base we have a module export called `Option` which we use very often. However, if we try to reference `Option` in a module where it's not currently imported, we will not get import suggestions/fixes for this. This is because there is already a (different) global type of the same name, provided by the `dom` `lib` types. I would like to be able to configure TypeScript and/or VS Code so that I do have import suggestions for `Option`. Suggestion: any time a module references a global value, and the project has a module export of the same name, provide an import suggestion for that. Potential caveat of this suggestion: what happens when you select "add all missing imports"? Ideally I would want it to import my `Option`, but what if I intentionally wanted to use the global version instead? ## Checklist My suggestion meets these guidelines: * [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, etc.) * [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).