Integrate Microsoft Agent Framework as the orchestration runtime

[KSemenenko]

Problem

dotPilot needs a single orchestration foundation for agents, workflows, sessions, HITL, and MCP-aware execution.

Scope

• Define how Agent Framework fits inside the embedded host
• Track agent sessions, workflows, middleware, context, and request-response use in dotPilot
• Clarify the boundary between Agent Framework and provider adapters

Out of scope

• Implementing provider-specific adapters themselves
• Telemetry exporter configuration beyond what this integration requires

Implementation notes

• Use Agent Framework as the preferred orchestration layer instead of inventing a parallel runtime
• Keep orchestration broad enough for coding and non-coding agents
• Align with the approved ADR and feature spec

Definition of Done

• The issue states the orchestration responsibilities and handoff points clearly
• The future provider and telemetry issues can reference this issue as their runtime anchor

Verification

• Review the issue against the feature spec session lifecycle and operator flows

Dependencies

• Parent epic: [Epic] Add the embedded agent runtime host to the Uno desktop app #12
• Depends on: Embed an Orleans silo in the Uno desktop host and register the core grains