Check the performance of all Cloudflare binding instrumentations

[JPeer264]

Description

A SQL-heavy Durable Object workload showed a large CPU regression in @sentry/cloudflare 10.61.0, caused by instrumentation work on every storage.sql.exec() call. This showed that the per-call cost of our Cloudflare instrumentations was not checked in a structured way.

Go over all instrumentations in @sentry/cloudflare and check their CPU cost, with tracesSampleRate: 1 and with tracesSampleRate: 0:

• Durable Object handlers and storage (SQL, KV, sync KV, alarms)
• Worker handlers (fetch, scheduled, queue, email, tail)
• Bindings (D1, R2, queue producer, service bindings and DO stubs, Workers AI)
• Agents
• Workflows

(follow up to #24655)

[linear-code]

JS-3827