Extend Turbopack's rule module types and its diagnostics for imports from non-ECMAScript modules.

- Allow `text` and `json` as public `turbopack.rules` module-type values, including configuration validation and the TypeScript configuration type.
- A file matched by a `type: 'text'` rule must export its exact source contents as a string. `type: 'raw'` must have the same behavior and remain a supported, non-deprecated alias of `text`; it must no longer produce an opaque module with no exports.
- The string behavior must work for ordinary imports and query-conditioned rules, including rules matching `?raw` for `import.meta.glob` usage. A `?raw` query is not implicit handling: the matching rule is what selects text/raw behavior.
- Preserve the existing meaning of `type: 'asset'` as emitting a file and exporting its URL.
- If an ECMAScript import tries to read a default, named, or namespace binding from a resolved module that cannot be placed in an ECMAScript chunk, compilation must report an error that identifies that module instead of silently producing `undefined`. Side-effect-only imports of such modules must continue to work.

Keep existing import-attribute behavior and the other configured module types working.