chore(deps): keep OpenTelemetry instrumentation and sdk-logs on 0.223

@vercel/otel 2.x peers on @opentelemetry/instrumentation and
@opentelemetry/sdk-logs at >=0.200.0 <0.300.0, but the vercel group
moved them to 0.300.0 and 3.0.0. 0.223.0 is the newest release in that
range and matches the api-logs bump. The Dependabot ignores stop the
group from pulling them past it again until @vercel/otel widens its
peers.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>

Author: ovflowd

.github/dependabot.yml

@@ -103,4 +103,9 @@ updates:
     ignore:
       - dependency-name: '@types/node'
         update-types: ['version-update:semver-major']
+      # @vercel/otel 2.x peers on these packages at <0.300.0
+      - dependency-name: '@opentelemetry/instrumentation'
+        versions: ['>=0.300.0']
+      - dependency-name: '@opentelemetry/sdk-logs'
+        versions: ['>=0.300.0']
     open-pull-requests-limit: 10

platforms/vercel/package.json

@@ -9,9 +9,9 @@
   },
   "dependencies": {
     "@opentelemetry/api-logs": "~0.223.0",
-    "@opentelemetry/instrumentation": "~0.300.0",
+    "@opentelemetry/instrumentation": "~0.223.0",
     "@opentelemetry/resources": "~1.30.1",
-    "@opentelemetry/sdk-logs": "~3.0.0",
+    "@opentelemetry/sdk-logs": "~0.223.0",
     "@vercel/analytics": "~2.0.1",
     "@vercel/otel": "~2.1.3",
     "@vercel/speed-insights": "~2.0.0"