ESM strict imports mode option to moduleResolution bundler

还没有人认领这个 Issue。

### 🔍 Search Terms

moduleResolution bundler esm 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

Add an option to enforce imports with file extension when the module is iESM (type: module) and moduleResolution is bundler.

### 📃 Motivating Example

For now in bundler moduleResolution, typescript is tolerent.
But when we develop a library, we have no idea of the strictness of the bundler (webpack is strict for example).
We need a way to enforce the imports with file extension in case the module is ESM

A dedicated option in the tsconfig can resolve it that we will enable or not

### 💻 Use Cases

1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?

首先审查编译器的 moduleResolution bundler 行为及其对 ESM (type: module) 导入的处理。定义提议的 tsconfig 选项应如何在不改变现有行为的情况下强制要求文件扩展名，然后为 strict 和 non-strict 配置添加覆盖测试。完成标准是：启用该选项时，bundler resolution 会报告不带扩展名的 ESM 导入。

由索引模型根据 Issue 内容生成。