Support source phase imports

### 🔍 Search Terms

import source wasm

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

Support for source phase imports: https://github.com/tc39/proposal-source-phase-imports

* https://github.com/nodejs/node/pull/56919
* https://github.com/denoland/deno_core/pull/1081

### 📃 Motivating Example

```ts
// wasmModule is WebAssembly.Module
import source wasmModule from "./math.wasm"
```

### 💻 Use Cases

1. Getting a wasm module instead of instance.

Start by reading the TC39 source phase imports proposal and the linked Node.js and Deno PRs. Use the motivating TypeScript example to define the expected type of the imported WebAssembly module and the supported syntax. Done means TypeScript accepts and correctly checks source phase imports without changing emitted JavaScript behavior.

Written by the indexing model from the issue text.