feat: add ExecutionType and AgentVersion as top-level span properties

[saksharthakkar]

Summary

• Add execution_type and agent_version fields to UiPathSpan dataclass
• Update to_dict() to return ExecutionType and AgentVersion as top-level keys
• Extract executionType and agentVersion from OTEL span attributes in otel_span_to_uipath_span()

Problem

Backend (LlmOps) expects ExecutionType and AgentVersion as top-level span properties, but Python SDK was sending them inside the Attributes JSON blob.

Before (broken)

{
  "Name": "Agent run - Agent",
  "ExecutionType": null,
  "AgentVersion": null,
  "Attributes": "{\"executionType\": 0, \"agentVersion\": \"1.0.0\", ...}"
}

After (fixed)

{
  "Name": "Agent run - Agent",
  "ExecutionType": 0,
  "AgentVersion": "1.0.0",
  "Attributes": "{...}"
}

Data Flow

Orchestrator → hdens → uipath-agents-python → uipath-python → LLMOps
                ↓              ↓                    ↓
         UIPATH_IS_DEBUG   executionType      ExecutionType (top-level)
      UIPATH_PROCESS_VERSION agentVersion     AgentVersion (top-level)

Component	Responsibility
Orchestrator	Sets JobFlags.IsStudioDebugContext
hdens	Propagates as UIPATH_IS_DEBUG and UIPATH_PROCESS_VERSION env vars
uipath-agents-python	Reads env vars, sets executionType/agentVersion in span attributes
uipath-python (this PR)	Extracts from attributes → top-level UiPathSpan fields
LLMOps	Receives top-level ExecutionType and AgentVersion for filtering

Related PRs

• hdens: https://github.com/UiPath/hdens/pull/6307
• uipath-agents-python: https://github.com/UiPath/uipath-agents-python/pull/86

LLMOps Compatibility

Backend expects these as top-level properties on the Span model:

• ExecutionType
• AgentVersion

Test plan

• Unit tests for execution_type extraction
• Unit tests for agent_version extraction
• Unit tests for both fields together
• Unit tests for missing fields (defaults to None)
• Integration test with env vars set

🤖 Generated with Claude Code

[JosephMar]

LGTM