fix: disable otelpgx pool.acquire spans in Datadog

[shyim]

Summary

• Disable otelpgx connection-pool acquire tracing via WithDisableAcquireTracer() when constructing the tracer in NewPool.
• Keeps query/exec/prepare spans and the existing sqlc SpanNameFunc naming from fix: use sqlc query names for otelpgx/Datadog DB span resources #791.
• No change to pool sizing, timeouts, or connection behavior.

Why

Prod emits high volumes of low-signal pool.acquire / client.request spans that add little monitoring value in Datadog.

Test plan

• mise run lint
• mise run test
• Confirm in Datadog APM that pool.acquire / related client.request noise drops while named DB query spans remain.

  

[greptile-apps]

Greptile Summary

The PR disables otelpgx connection-pool acquire spans to reduce low-signal Datadog telemetry while retaining existing database operation tracing.

• Adds WithDisableAcquireTracer() when constructing the shared database tracer.
• Leaves pool configuration, SQL span naming, and query/exec/prepare tracing unchanged.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The pinned otelpgx version supports the new option, and its scoped behavior suppresses pool-acquire tracing without changing pool operation or the existing query span instrumentation.

Important Files Changed

Filename	Overview
api/internal/database/db.go	Adds the supported acquire-tracer opt-out to the shared pool tracer configuration without affecting connection behavior or database-operation spans.

_{Reviews (1): Last reviewed commit: "fix: disable otelpgx pool.acquire spans ..." | Re-trigger Greptile}