Python: Prefer runtime kwargs for conversation_id in OpenAI Responses client

[giles17]

Motivation and Context

Fixes stale tool-call routing by preferring the freshest conversation_id propagated via runtime kwargs

Resolves #3304

Description

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[markwallace-microsoft]

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
packages/core/agent_framework/openai
_responses_client.py	560	117	79%	250, 255, 257–258, 269, 287, 295, 298–305, 307, 311–312, 314–323, 329, 334–338, 340–341, 343, 380, 412, 437, 443, 461–462, 484, 489, 545, 559, 576, 589, 644, 723, 728, 732–734, 738–739, 762, 777–778, 782–784, 831, 853–854, 869–870, 888–889, 978–979, 988–989, 1020–1021, 1037, 1039, 1114–1122, 1145–1151, 1170, 1188–1189, 1198, 1203–1205, 1211–1212, 1225, 1240, 1276–1277, 1279–1281, 1295–1297, 1307–1308, 1314, 1329
TOTAL	17437	2701	84%

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
3176	213 💤	0 ❌	0 🔥	1m 4s ⏱️

[Copilot]

Pull request overview

This PR fixes a critical bug in tool-call routing by changing the priority order for conversation_id retrieval. The fix ensures that runtime-updated conversation IDs (passed via kwargs during tool execution loops) take precedence over the initial configuration (stored in options dict).

Changes:

• Modified _get_current_conversation_id to check kwargs before options, ensuring fresh conversation IDs from tool execution loops are used instead of stale initial values