fix(cloudflare): Auto-instrument classes re-exported from the worker entry - #23282

Agents are different, they need special care on top of the wrangler config. Because they are marked as DurableObjects, but have a different wrapper, they need extra hacks within the Vite plugin.

Issue

Before, specific type of import/exports didn't work properly and caused manual instrumentation again: https://github.com/sergical/cuzz/blob/4ec6080865e37491ff240007bbe886f907ad1de7/src/worker/index.ts#L11-L15

Solution(s)

First one

We had to add a agent return inside resolveWrapperKind, to correctly identify Agents in there as well, so we know when to add instrumentAgentWithSentry instead of instrumentDurableObjectWithSentry

Second one

When a class gets exported right away, we need to change that export:

export { MyAgent, MyDo } from './do' 

needs to be changed to the following in order to wrap it:

import { MyAgent as __SENTRY_REEXPORT_MyAgent__, MyDo as __SENTRY_REEXPORT_MyDo__ } from './do' 
const __SENTRY_WRAPPED_MyDurableObject__ = __SENTRY__.instrumentDurableObjectWithSentry((env) => ({}), __SENTRY_REEXPORT_MyDurableObject__);
export { __SENTRY_WRAPPED_MyAgent__ as MyAgent, __SENTRY_WRAPPED_MyDo__ as MyDo } from './do' 

This should fix what was needed before: getsentry/sentry-docs#18944

Clanker description

The Vite auto-instrument transform only wrapped classes declared in the entry module. An entry that just aggregates its Durable Objects, Agents and Workflows from other files — import { MyAgent } from './agent'; export { MyAgent }, or export { MyAgent } from './agent' — got no instrumentation at all, leaving manual instrument*WithSentry wrapping as the only option.

An import binding cannot be reassigned, so instead of renaming a declaration the transform now re-points those specifiers at a fresh wrapper binding and rebuilds the export statement, carrying unrelated specifiers over verbatim.

Agent detection was blind to the same shapes: collectAgentCandidates only considered local classes, so a re-exported Agent was never even offered to the cross-module base-class walk that already knew how to resolve it.

Star re-exports (export * from './do') still cannot be wrapped — they name no binding — so the warning stays, reworded to say that rather than blaming re-exports in general.