ESM strict imports mode option to moduleResolution bundler

Nadie ha tomado este issue todavía.

### 🔍 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?

Empieza revisando el comportamiento de moduleResolution bundler del compilador y cómo gestiona las importaciones ESM (type: module). Define cómo la opción propuesta de tsconfig debe exigir extensiones de archivo sin cambiar el comportamiento existente y, después, añade cobertura para configuraciones strict y non-strict. Se considera completado cuando bundler resolution informa de las importaciones ESM sin extensión al habilitar la opción.

Escrito por el modelo de indexación a partir del texto del issue.