Shouldn't TypeScript be able to polyfill `import defer` with `Proxy` to work with `"module": "commonjs"`?

### 🔍 Search Terms

import defer commonjs
import defer require

### ✅ 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

Since the TypeScript beta announcement, I tried it in the playground. But setting `"module"` to `"commonjs"` sadly revealed that `import defer` only work with `"module": "esnext"` or `"module": "preserve"`.

But `Proxy` can polyfill this exact behavior.

### 📃 Motivating Example

This code:

```typescript
import defer * as MyModule from 'my-module'
```

should output something like this:

```javascript
let _module
const MyModule = new Proxy({}, {
get(_target, prop) {
if (!_module) {
_module = require('my-module') // the real code would obviously more complicated as it needs to force `_module` to be an object
}
return _module[prop]
}
})
```

### 💻 Use Cases

1. What do you want to use this for? Using `import defer` for legacy targets
2. What shortcomings exist with current approaches? `await import` forces `Promise`
3. What workarounds are you using in the meantime? `await import`

まず、`module` が `commonjs` の場合に TypeScript が `import defer` をどのように扱うかを追跡し、それを既存の `esnext` と `preserve` の動作と比較します。動機となった `Proxy` の例と、示されているレガシーターゲットのユースケースを使って期待される出力を定義し、その後、`Promise` を導入せずに同期的な遅延アクセスが機能するかを示すカバレッジを追加します。

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