Temporal: Braintrust Temporal for ESM projects and fix merging of WorkflowClientInterceptors

[cpinn]

This PR adds an improvement to our temporal integration to work in esm environments and fixes an issue with the use of the older WorkflowClientInterceptors.

Additional examples have been added:

• ESM project
• Example with BraintrustTemporalPlugin, AISdkPlugin and wrapAISDK

[cpinn]

@ibolmo (and @clutchski since you wrote the python implementation and my know more about temporal in general)

I plan to split this example into two different examples to illustrate the issues I have been BraintrustTemporalPlugin and AISDKPlugin working together.

The two different workflows I have found are:

1. The BraintrustTemporalPlugin works with just wrapAISDK (no AISDKPlugin) if you create activities in temporal for llm calls.
2. I found one way of making the AISDKPlugin work with the BraintrustTemporalPlugin (make sure our plugin is registered first) and only wrap the underlying model provider.

// this will wrap just the doGenerate call and map it with out temporal flows
const tracedProvider = wrapAISDKProvider(openai as any);

  const worker = await Worker.create({
    connection,
    namespace: "default",
    taskQueue: TASK_QUEUE,
    // Load the workflows from this example's `src` so the exported
    // workflow functions (`haikuAgent`, `haikuAgentTraced`, etc.) are available.
    workflowsPath: new URL("./workflows.ts", import.meta.url).pathname,
    activities: { getWeather },
    plugins: [
      new AiSdkPlugin({ modelProvider: tracedProvider }),
      new BraintrustTemporalPlugin(),
    ],

The advantage of the temporal AISDKPlugin is that the plugin can work without creating explicit activities for the llm calls but it does that by a low level wrapping which means the trace looks less detailed if I just wrap the model.

What you get with creating activities and using wrapAISDK (which does not support the temporal aisdk plugin type)

What you get with wrapping just the Model Provider

What the user was getting when trying to currently use our workflow integration with just the AISDKPlugin

I am still looking into what might work to wrap the entire plugin but haven't figured it out yet and wondering if I should push out something that sort of works with the model provider wrapping or if that is not that useful.

[cpinn]

This is the important change for ESM to work, Temporal is able to bundle the package by name.

[cpinn]

This was leading to our plugin being dropped when registered with another plugin (ie. AISDKPlugin).

[cpinn]

This is temp until I decide what I wish to do for the temporal integration

1. Drop attempting to wrap the temporal plugin and just merge the fix for making our plugin work
2. Add this simple wrapping on the model
3. Continue the quest to figure out how to integrate with the plugin