feat: auto-inject conversation id into Orchestrator/Maestro tool calls

[maxduu]

Summary

Process-type tools whose input schemas declare a UIPATH_RESERVED_CONVERSATIONID top-level argument now receive the current conversation id automatically. The runtime value always overrides any caller-supplied value; when no conversation id is available, the injection silently no-ops.

The conversation id is read from os.environ["UIPATH_CONVERSATION_ID"], which is populated by UiPathRuntimeContext.with_defaults() (see UiPath/uipath-runtime-python#114). Resolution covers fpsProperties.conversationalService.conversationId from uipath.json. This PR depends on that runtime change to land first.

Test plan

• tests/agent/tools/test_process_tool.py::TestProcessToolConversationIdInjection — 4 new tests:
  • injects when schema declares the field
  • runtime value overrides caller-supplied value
  • silently omits when conversation id missing
  • skips injection when schema doesn't declare the field
• Existing 21 process_tool tests still pass
• End-to-end smoke: run a conversational agent with a Maestro flow tool whose input schema declares UIPATH_RESERVED_CONVERSATIONID; confirm Orchestrator receives the conversation id in input_arguments

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud