Update dependency @types/jsdom to v28

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@types/jsdom (source)	^21.1.7 → ^28.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 2 workspace projects
? Verifying lockfile against supply-chain policies (882 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 80, reused 0, downloaded 0, added 0
Progress: resolved 88, reused 0, downloaded 1, added 0
Progress: resolved 89, reused 0, downloaded 1, added 0
Progress: resolved 128, reused 0, downloaded 1, added 0
Progress: resolved 266, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (882 entries in 10.5s)
[ERR_PNPM_MISSING_TARBALL_INTEGRITY] 1 lockfile entries failed verification:
  y-codemirror.next@0.3.5 has no "integrity" field, so its downloaded tarball cannot be verified

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.