build: relax wrapt version constraint in pyproject.toml

[Atry]

Description

Relax the wrapt version constraint from < 2.0.0 to < 3.0.0 to allow compatibility with wrapt 2.x.

Fixes #3903

Background

The current constraint wrapt >= 1.0.0, < 2.0.0 unnecessarily prevents users from using wrapt 2.x. This is an unnecessary limitation because the APIs used by opentelemetry-instrumentation (wrap_function_wrapper and ObjectProxy) remain compatible in wrapt 2.x.

Changes

Updated the wrapt version constraint in the following packages:

• opentelemetry-instrumentation
• opentelemetry-processor-baggage
• 19 instrumentation packages:
  • opentelemetry-instrumentation-aio-pika
  • opentelemetry-instrumentation-aiohttp-client
  • opentelemetry-instrumentation-aiohttp-server
  • opentelemetry-instrumentation-aiopg
  • opentelemetry-instrumentation-asyncio
  • opentelemetry-instrumentation-boto3sqs
  • opentelemetry-instrumentation-cassandra
  • opentelemetry-instrumentation-click
  • opentelemetry-instrumentation-confluent-kafka
  • opentelemetry-instrumentation-dbapi
  • opentelemetry-instrumentation-elasticsearch
  • opentelemetry-instrumentation-grpc
  • opentelemetry-instrumentation-httpx
  • opentelemetry-instrumentation-jinja2
  • opentelemetry-instrumentation-pika
  • opentelemetry-instrumentation-pymemcache
  • opentelemetry-instrumentation-pyramid
  • opentelemetry-instrumentation-threading
  • opentelemetry-instrumentation-urllib3

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Verified that uv lock --check passes (the locked wrapt version in uv.lock remains unchanged)
• The change only relaxes upper bound constraints, so existing functionality is preserved

Does This PR Require a Core Repo Change?

• [x] No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• [x] Followed the style guidelines of this project
• [x] Changelogs have been updated
• [ ] Unit tests have been added
• [ ] Documentation has been updated