fix: create session sync client before metadata extraction

[vinhnxv]

Summary

• Move session creation before extractSDKMetadataAsync callback
• Reuse existing session instance instead of creating new one inside callback

Problem

The session sync client was being created inside the extractSDKMetadataAsync callback:

extractSDKMetadataAsync(async (sdkMetadata) => {
    api.sessionSyncClient(response).updateMetadata(...) // Creates new client each time
});

const session = api.sessionSyncClient(response); // Another instance created here

This could lead to race conditions with multiple session client instances.

Solution

Create the session client once, before the async metadata extraction:

const session = api.sessionSyncClient(response); // Create FIRST

extractSDKMetadataAsync(async (sdkMetadata) => {
    session.updateMetadata(...) // Reuse existing instance
});

Test Plan

• Verify session metadata updates correctly
• Check no duplicate session clients are created