Drop @opentelemetry/api from peerDependencies

[candrewlee14]

Small one, from #6115.

Why

@opentelemetry/api is only used for types in src/tracing.ts, and the runtime import is commented out:

import type { Span, Tracer } from '@opentelemetry/api';
let otel: typeof import('@opentelemetry/api') | undefined;
// try {
// 	otel = await import('@opentelemetry/api');
// } catch (err: any) { ... }

So otel is never assigned and startActiveSpan always takes the if (!otel) return fn() path. tracer is @internal and isn't exported from the public entry, so published 1.0.0-rc.1 has no runtime or .d.ts reference to it.

It's already in devDependencies, so types still resolve when you build.

What it fixes

Listing it as an optional peer makes package managers that install a separate copy per peer combination give each consumer its own copy of drizzle-orm. TypeScript then treats those copies as unrelated, so values like SQL stop being assignable between packages in a workspace. In ours that was one of the causes of ~50 type errors.

This drops one cause of that and costs nothing here.

Scope

Four deleted lines in drizzle-orm/package.json. No code changes. If you'd rather keep the peer entry for documentation, feel free to close — the other suggestions in #6115 are the larger part.

[hknakn]

Verified against main: the @opentelemetry/api import in src/tracing.ts is type-only with the runtime await import commented out, nothing else under drizzle-orm/src references it, and it's already in devDependencies at the same ^1.4.1. No-op at runtime and for published types.

We're hit by the wider issue in #6115 — the expo-sqlite entry puts 76 Expo/RN packages into our Node images. Opened #6219 for that one.

This looks safe to merge on its own.