fix: support OpenTelemetry 1.39+ by relaxing version constraints

The <1.39.0 upper bound on opentelemetry-api and opentelemetry-sdk was
added due to agent_engines exporter constraints in
google-cloud-aiplatform. The upstream package (v1.141.0) now allows
opentelemetry-sdk<2, so this constraint is no longer needed.

The opentelemetry-exporter-gcp-logging package was also updated upstream
(1.10.0a0+) to require opentelemetry-sdk>=1.39.0, confirming the
ecosystem has moved past the old cap.

Relaxes both opentelemetry-api and opentelemetry-sdk to <2.0.0.

Fixes #4898

Author: brucearctor

pyproject.toml

@@ -49,13 +49,13 @@ dependencies = [
   "httpx>=0.27.0, <1.0.0",                                   # HTTP client library
   "jsonschema>=4.23.0, <5.0.0",                              # Agent Builder config validation
   "mcp>=1.24.0, <2.0.0",                                     # For MCP Toolset
-  "opentelemetry-api>=1.36.0, <1.39.0",                      # OpenTelemetry - keep below 1.39.0 due to current agent_engines exporter constraints.
+  "opentelemetry-api>=1.36.0, <2.0.0",                       # OpenTelemetry
   "opentelemetry-exporter-gcp-logging>=1.9.0a0, <2.0.0",
   "opentelemetry-exporter-gcp-monitoring>=1.9.0a0, <2.0.0",
   "opentelemetry-exporter-gcp-trace>=1.9.0, <2.0.0",
   "opentelemetry-exporter-otlp-proto-http>=1.36.0",
   "opentelemetry-resourcedetector-gcp>=1.9.0a0, <2.0.0",
-  "opentelemetry-sdk>=1.36.0, <1.39.0",
+  "opentelemetry-sdk>=1.36.0, <2.0.0",
   "pyarrow>=14.0.0",
   "pydantic>=2.12.0, <3.0.0",                                 # For data validation/models
   "python-dateutil>=2.9.0.post0, <3.0.0",                    # For Vertext AI Session Service