Take TypeScript 7 and eslint 10 when eslint-config-next can

`.github/dependabot.yml` ignores major bumps of `typescript` and `eslint`. This is the note that
says when to take them out, so the ignore does not become permanent by forgetting.

Both are blocked by the same thing, and neither by anything this repository pins. `eslint-config-next@16.3.4`
vendors `typescript-eslint@8.68.0` and the eslint plugins, and Next pins that config:

| what | who refuses it | range |
| --- | --- | --- |
| typescript 7 | `typescript-eslint@8.68.0` | `>=4.8.4 <6.1.0` |
| eslint 10 | `eslint-plugin-import@2.32.0` | up to `^9` |
| eslint 10 | `eslint-plugin-jsx-a11y@6.10.2` | up to `^9` |
| eslint 10 | `eslint-plugin-react@7.37.5` | up to `^9.7` |

The typescript one is a hard failure, not a warning: `npm run lint` exits 2 with "typescript-eslint
does not support TS 7.0". The eslint one makes `npm ls` report the package as invalid, and the SBOM
job runs `npm ls`, so that fails too. #95 was the pull request that proved both.

`typescript-eslint` accepts eslint 10 already, so eslint is likely to clear first, when those three
plugins ship a release that accepts 10.

**How to check:**

```bash
npm ls eslint-config-next typescript-eslint
node -e "console.log(require('./node_modules/eslint-config-next/node_modules/typescript-eslint/package.json').peerDependencies)"
```

When the vendored range covers the major, remove that entry from the `ignore` list in
`.github/dependabot.yml` and let dependabot propose it again.

Start with .github/dependabot.yml and inspect the installed dependency ranges using the two npm and Node commands in the issue. Wait until the vendored ranges accept TypeScript 7 and ESLint 10, then remove the corresponding major-version ignore entries and let Dependabot propose the updates again.

Written by the indexing model from the issue text.