docs: clarify tsconfig resolution for each file

[shulaoda]

Description

Follow-up to #22695 (upgrade to Rolldown 1.1.2). The old wording "Vite uses the tsconfig.json in the closest parent directory" was inaccurate: Vite walks up the directory tree and uses the closest tsconfig.json that matches the file, not simply the closest one.

The docs now state that:

• A config matches based on its files, include, and exclude fields, or those of one of its references.
• The search continues upward when a config doesn't match.
• No options are applied when no tsconfig.json matches the file.

Docs-only change.

Notes for reviewers

Reference: #22695, Rolldown v1.1.2, and the tsconfig input option docs.

[sapphi-red]

Suggested change

	Vite respects some of the options in `tsconfig.json` and sets the corresponding Oxc Transformer options. For each file, Vite uses the closest parent `tsconfig.json` that matches the file:
	- A `tsconfig.json` matches when the file satisfies its [`files`](https://www.typescriptlang.org/tsconfig/#files), [`include`](https://www.typescriptlang.org/tsconfig/#include), and [`exclude`](https://www.typescriptlang.org/tsconfig/#exclude) fields, or those of one of the config files listed in its [`references`](https://www.typescriptlang.org/tsconfig/#references) field.
	- If a `tsconfig.json` doesn't match, Vite keeps searching parent directories upward.
	- If no `tsconfig.json` matches the file, none of these options are applied.
	Vite respects some of the options in `tsconfig.json` and sets the corresponding Oxc Transformer options. For each file, Vite uses the closest parent `tsconfig.json` or the config referenced by the [`references`](https://www.typescriptlang.org/tsconfig/#references) field in them if that config matches the file. Vite treats the config to match a file when the file satisfies the config's [`files`](https://www.typescriptlang.org/tsconfig/#files), [`include`](https://www.typescriptlang.org/tsconfig/#include), and [`exclude`](https://www.typescriptlang.org/tsconfig/#exclude) fields.

I think the last 2 items are already implied in the sentence.

[shulaoda]

Agreed on merging into one paragraph and dropping the "no match, no options" part as implied. I'd just keep the wording as the closest parent tsconfig.json that matches the file (relative clause) rather than if that config matches, so the walk-up when it doesn't match isn't lost.