chore(deps): update dependency mypy to v2.0.0

[descope]

This PR contains the following updates:

Package	Type	Update	Change	Pending	OpenSSF
mypy (changelog)	dependency-groups	patch	==1.11.2 → ==2.0.0	2.1.0

---

Configuration

📅 Schedule: (in timezone Asia/Jerusalem)

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

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ Rebasing: Never, 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 has been generated by Mend Renovate.

[descope]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: uv.lock

Command failed: uv lock --upgrade-package mypy
Using CPython 3.14.5 interpreter at: /opt/containerbase/tools/python/3.14.5/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version > '3.9' and python_full_version < '3.10'):
  ╰─▶ Because the requested Python version (>=3.9, <4.0) does not satisfy
      Python>=3.10 and descope:types depends on mypy{python_full_version <
      '3.10'}==2.0.0, we can conclude that descope:types's requirements are
      unsatisfiable.
      And because your project requires descope:types, we can conclude that
      your project's requirements are unsatisfiable.

hint: While the active Python version is 3.14, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python versions using `requires-python`.

File name: pyproject.toml

Artifact update for mypy resolved to version 2.1.0, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 2.0.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

File name: pyproject.toml

Artifact update for mypy resolved to version 2.1.0, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 2.0.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/