fix(deps): update dependency typescript to v7

The Mendral bot already flagged the lockfile and peer-conflict issues here, and they're right — this can't install. But beyond install: this is the root devDependencies TypeScript pin. Bumping it to 7.0.2 without simultaneously updating the toolchain that consumes it — @swc-node/register (< 7), ts-node, typedoc, @typescript-eslint/eslint-plugin (< 6.1.0) — is changing the compiler without telling the tools that depend on it. The package.json diff looks like a one-liner, but the blast radius includes every dev tool in the repo that has a peer constraint on typescript. Mendral named the two that block install; the full list is longer.

This is a dependencies entry, not a devDependencies entry — TypeScript is a runtime dependency of the flake-linter package, meaning it uses the compiler API at runtime (likely for AST analysis of test files). The bump here has a different consequence than the root bump: every downstream consumer of @clipboard-health/playwright-flake-linter will resolve TypeScript 7.0.2 at runtime, not just at build time. If the flake-linter's TypeScript API usage hits a 6.x or 7.x breaking change, it fails at runtime in the consumer's CI, not at build time in this repo. The surface area of this change is wider than the root bump — it's worth separating these two decisions.

Is there a TypeScript migration plan for this repo? Jumping from 5.9.3 to 7.0.2 skips the entire 6.x line — that's not a routine Renovate bump, it's a cross-major compiler migration. If the org has a plan (e.g., upgrading toolchain dependencies first, then running the type-checker across all packages, then reviewing the compiler output), this PR is premature. If there isn't a plan, the right move is probably to close this and let Renovate's ignore notification do its job until the toolchain catches up.