fix(openai-realtime): remove buggy resolveGeneration method that used wrong key lookup

[toubatbrian]

• Fixes [Detail Bug] Realtime: resolveGeneration looks up by server responseId instead of client eventId, causing generateReply() to hang on function calls #968
• Removes the resolveGeneration method which incorrectly looked up futures using responseId (server-generated) instead of eventId (client-generated)
• Aligns with the Python implementation which does not have a resolveGeneration method

Problem

When generateReply() was called and the AI returned a function call (non-message item), handleResponseOutputItemAdded called resolveGeneration(responseId). This method tried to look up responseCreatedFutures[responseId], but futures were stored with eventId (client-generated), causing the lookup to fail.

The future was already correctly resolved in handleResponseCreated using client_event_id from response metadata, making resolveGeneration both redundant and buggy.

[changeset-bot]

🦋 Changeset detected

Latest commit: efdeacf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 17 packages

Name	Type
@livekit/agents-plugin-openai	Patch
@livekit/agents-plugin-anam	Patch
@livekit/agents-plugin-cartesia	Patch
@livekit/agents-plugin-elevenlabs	Patch
@livekit/agents-plugin-google	Patch
@livekit/agents-plugin-inworld	Patch
@livekit/agents-plugin-neuphonic	Patch
@livekit/agents-plugin-resemble	Patch
@livekit/agents-plugin-rime	Patch
@livekit/agents-plugin-xai	Patch
@livekit/agents	Patch
@livekit/agents-plugin-baseten	Patch
@livekit/agents-plugin-bey	Patch
@livekit/agents-plugin-deepgram	Patch
@livekit/agents-plugin-livekit	Patch
@livekit/agents-plugin-silero	Patch
@livekit/agents-plugins-test	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR