fix(deps): update dependency wrapt to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
wrapt (changelog)	~=1.17.3 → ~=2.2.1

---

Release Notes

GrahamDumpleton/wrapt (wrapt)

v2.2.1: wrapt 2.2.1

Compare Source

Full release notes: https://wrapt.readthedocs.io/en/latest/changes.html#version-2-2-1

Install from PyPi (recommended):

pip install wrapt==2.2.1

PyPi uploads follow each GitHub release; if pip reports the
version is unavailable, the matching PyPi upload may not have
happened yet.

Pre-built wheels are provided for a range of Python versions
and platforms (Linux x86_64/aarch64/riscv64, macOS x86_64 and
arm64, Windows x86_64 and arm64, plus PyPy and free-threaded
builds). The source distribution is also attached together
with SHA256SUMS for verification.

v2.2.0: wrapt 2.2.0

Compare Source

Full release notes: https://wrapt.readthedocs.io/en/latest/changes.html#version-2-2-0

Install from PyPi (recommended):

pip install wrapt==2.2.0

PyPi uploads follow each GitHub release; if pip reports the
version is unavailable, the matching PyPi upload may not have
happened yet.

Pre-built wheels are provided for a range of Python versions
and platforms (Linux x86_64/aarch64/riscv64, macOS x86_64 and
arm64, Windows x86_64 and arm64, plus PyPy and free-threaded
builds). The source distribution is also attached together
with SHA256SUMS for verification.

v2.1.2: wrapt-2.1.2

Compare Source

See the project page on the Python Package Index at https://pypi.org/project/wrapt/2.1.2/ for more information.

v2.1.1: wrapt-2.1.1

Compare Source

See the project page on the Python Package Index at https://pypi.org/project/wrapt/2.1.1/ for more information.

v2.1.0: wrapt-2.1.0

Compare Source

See the project page on the Python Package Index at https://pypi.org/project/wrapt/2.1.0/ for more information.

v2.0.1: wrapt-2.0.1

Compare Source

See the project page on the Python Package Index at https://pypi.org/project/wrapt/2.0.1/ for more information.

v2.0.0: wrapt-2.0.0

Compare Source

See the project page on the Python Package Index at https://pypi.org/project/wrapt/2.0.0/ for more information.

---

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: uv.lock

Command failed: uv lock --upgrade-package wrapt
Using CPython 3.14.5 interpreter at: /opt/containerbase/tools/python/3.14.5/bin/python3.14
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version >= '3.13'):
  ╰─▶ Because opentelemetry-instrumentation>=0.59b0,<=0.61b0 depends
      on wrapt>=1.0.0,<2.0.0 and only the following versions of
      opentelemetry-instrumentation are available:
          opentelemetry-instrumentation<=0.59b0
          opentelemetry-instrumentation==0.60b0
          opentelemetry-instrumentation==0.60b1
          opentelemetry-instrumentation==0.61b0
          opentelemetry-instrumentation==0.62b0
          opentelemetry-instrumentation==0.62b1
          opentelemetry-instrumentation==0.63b0
          opentelemetry-instrumentation==0.63b1
      we can conclude that opentelemetry-instrumentation>=0.59b0,<0.62b0
      depends on wrapt>=1.0.0,<2.0.0.
      And because opentelemetry-instrumentation==0.62b0
      depends on opentelemetry-semantic-conventions==0.62b0
      and opentelemetry-semantic-conventions==0.62b0
      depends on opentelemetry-api==1.41.0, we
      can conclude that opentelemetry-api!=1.41.0,
      opentelemetry-instrumentation>=0.59b0,<0.62b1, all of:
          wrapt<1.0.0
          wrapt>=2.0.0
       are incompatible.
      And because opentelemetry-instrumentation==0.62b1
      depends on opentelemetry-semantic-conventions==0.62b1
      and opentelemetry-semantic-conventions==0.62b1 depends on
      opentelemetry-api==1.41.1, we can conclude that all of:
          opentelemetry-api<1.41.0
          opentelemetry-api>1.41.1
      , opentelemetry-instrumentation>=0.59b0,<0.63b0, all of:
          wrapt<1.0.0
          wrapt>=2.0.0
       are incompatible.
      And because opentelemetry-instrumentation==0.63b0
      depends on opentelemetry-semantic-conventions==0.63b0
      and opentelemetry-semantic-conventions==0.63b0 depends on
      opentelemetry-api==1.42.0, we can conclude that all of:
          opentelemetry-api<1.41.0
          opentelemetry-api>1.42.0
      , opentelemetry-instrumentation>=0.59b0,<0.63b1, all of:
          wrapt<1.0.0
          wrapt>=2.0.0
       are incompatible.
      And because opentelemetry-instrumentation==0.63b1
      depends on opentelemetry-semantic-conventions==0.63b1
      and opentelemetry-semantic-conventions==0.63b1 depends
      on opentelemetry-api==1.42.1, we can conclude that
      opentelemetry-api<1.41.0, opentelemetry-instrumentation>=0.59b0, all of:
          wrapt<1.0.0
          wrapt>=2.0.0
       are incompatible.
      And because your project depends on opentelemetry-api>=1.39.1,<1.40.dev0
      and opentelemetry-instrumentation>=0.59b0, we can conclude that your
      project depends on wrapt>=1.0.0,<2.0.0.
      And because your project depends on wrapt>=2.2.1,<2.3.dev0 and your
      project requires basalt-sdk[all], we can conclude that your project's
      requirements are unsatisfiable.