fix: update test expectations for GitHub tools in campaign orchestrators

[Copilot]

Updates the test suite to reflect the architectural change that allows campaign orchestrators to have GitHub tool access for discovery operations.

Changes:

• Updated TestBuildOrchestrator_DispatchOnlyPolicy to expect GitHub tools to be configured in orchestrators
• Changed test assertion from expecting NO GitHub tools to expecting GitHub tools with repos, issues, and pull_requests toolsets
• Updated test comment to clarify: "Orchestrators should have GitHub tool access for discovery operations"

Before:

// Orchestrators should not have GitHub tool access to the agent.
if data.Tools != nil {
    if _, ok := data.Tools["github"]; ok {
        t.Fatalf("expected orchestrator to omit github tools")
    }
}

After:

// Orchestrators should have GitHub tool access for discovery operations
if data.Tools == nil {
    t.Fatalf("expected Tools to be configured")
}
if _, ok := data.Tools["github"]; !ok {
    t.Fatalf("expected orchestrator to have github tools configured")
}

This change aligns with the new architecture where orchestrators can perform GitHub API operations directly rather than being limited to only dispatching workflows.

---

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

[mnkiefer]

@copilot We no longer have the architectural constraint that orchestrators only coordinate via dispatch-workflow

[Copilot]

@copilot We no longer have the architectural constraint that orchestrators only coordinate via dispatch-workflow

Updated in commit 26c198a. Restored the GitHub tools configuration for orchestrators and updated the test to reflect the new architecture where orchestrators can have GitHub tool access for discovery operations.