Add DTS workflow display names

[Tsuyoshi Ushio (TsuyoshiUshio)]

Purpose

• Add durabletask.displayName tags so the DTS dashboard shows meaningful Dynamic Workflow orchestration and Activity labels instead of shared registered Function names.
• Label orchestrations as <agent_name>-orchestration, tool Activities by workflow tool name, and Workflow Sub Agent Activities by agent slug.
• Use the public native two-argument Durable Task orchestrator API required for Activity tags while preserving workflow execution behavior.

Fix

#92
https://github.com/Azure/azure-functions-bucees-planning/issues/1302

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone https://github.com/Azure/azure-functions-agents-runtime.git
cd azure-functions-agents-runtime
git checkout tsuyoshiushio-investigate-dts-activity-names
pip install -e .[dev]

• Test the code

python -m ruff check src tests
python -m mypy src
python -m pytest --cache-clear --cov=./src/azure_functions_agents --cov-report=xml --cov-branch tests

• For DTS emulator validation, run samples/workflow-incident-triage with Task Hub default, start a workflow, and inspect http://localhost:8082.

Locally tested with the dts-emulator. Azure one also works.

What to Check

Verify that the following are valid:

• Registered Function names remain agents_workflow_orchestrator, agents_workflow_run_tool, and agents_workflow_run_sub_agent.
• DTS shows the derived orchestration label and concrete tool/Sub Agent Activity labels.
• Static and data-driven workflows retain scheduling, cancellation, timer, status, and authorization behavior.

Other Information

• Extends the existing Dynamic Workflows design in FRD 0004; no new FRD or authoring field is introduced.
• Different Function apps must not share the same DTS Task Hub because workers can expose different orchestrator/activity sets.
• Follow-up: migrate the remaining workflow client compatibility aliases to the native Durable APIs in Migrate workflow client operations to native Durable APIs #202.