Document orchestration discovery and method probing behavior in analyzers

[Copilot]

PR #284 discussion identified the need to formally document how orchestration analyzers discover orchestrations and follow method call chains.

Changes

Added comprehensive documentation to src/Analyzers/CONTRIBUTING.md covering:

• Orchestration Discovery: How the analyzer identifies three orchestration patterns (Durable Functions with [OrchestrationTrigger], TaskOrchestrator classes, and AddOrchestratorFunc lambdas)

• Method Probing Algorithm: Recursive traversal with cycle detection, cross-tree analysis, and concurrent execution support

• Probing Capabilities: Direct calls, static/instance methods, async methods, lambdas, method references, partial classes, recursive methods

• Probing Limitations: Cannot follow interface/abstract/virtual method calls, external libraries, reflection, or DI-resolved instances

• Diagnostic Message Format: Explicitly identifies the violating method, the specific violation, and the invoking orchestration

Example limitation documented:

// Will NOT be analyzed
IHelper helper = GetHelper(); // implementation unknown
helper.DoSomething(); // analyzer cannot follow this call

This provides the specification needed for consistent analyzer development and explains expected behavior to users.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Roslyn Analyzer: document how orchestrations are analyzed and the method probing is executed.</issue_title>
<issue_description>Please see the discussion in #284</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Roslyn Analyzer: document how orchestrations are analyzed and the method probing is executed. #286

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.