docs: note tsconfig include changes with a custom distDir (#101963)
### What?
Adds a short **Custom `distDir`** note to the TypeScript config docs:
Next.js updates `tsconfig.json` to include the generated types in your
`distDir`, so if you change `distDir` you may need to manually remove
the old paths from `include`.
### Why?
Several reports ([agent-feedback
finding](https://next-maintainer-agent.vercel.tools/agent-feedback/7128))
describe `next dev` / `next build` with an alternate `distDir` leaving
extra `include` entries in a committed `tsconfig.json`. Reproduced on
`16.5.0-canary.53` with `next build`, `next dev` and `next typegen`:
each appended `<distDir>/types/**/*.ts` and
`<distDir>/dev/types/**/*.ts`, and the entries stayed after the
directory was deleted.
This is longstanding behavior (see #55249), not a recent regression; no
release boundary was bisected. Changing how Next.js edits
`tsconfig.json` is harder and riskier, so for now this documents the
behavior and leaves runtime code unchanged.
Related: #55249
### Verification
- `npx prettier@3.6.2 --check
docs/01-app/03-api-reference/05-config/02-typescript.mdx`
- Manual repro on `next@16.5.0-canary.53` in a minimal App Router app
with `distDir: process.env.NEXT_DIST_DIR || '.next'`. `next build`,
`next dev` and `next typegen` each appended include entries for the
custom dir and repointed `next-env.d.ts`.
- Not run: docs link validation locally (runs in CI).
<!-- NEXT_JS_LLM -->
<!-- fleet 9d7a4a4d-880b-4ebd-acf5-26e96c5e946a -->
---------
Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Co-authored-by: Vercel Fleet <fleet@vercel.com>
Co-authored-by: Luke Sandberg <210140+lukesandberg@users.noreply.github.com>