Add conditions to choose ConnectorClient scope

[sw-joelmut]

Fixes #723

Description

This PR adds a condition to only use the azp and appid JWT identity values when the Activity.Recipient.Role is Skill, otherwise will resolve api.botframework.com as scope.

Testing

The following image shows the Agent to Agent operations using MSTeams and WebChat

[Copilot]

Pull request overview

This PR fixes a 401 authentication error that occurs when using TeamsInfo.getMember on incoming webhooks by implementing role-based scope resolution for ConnectorClient authentication. The solution differentiates between agent-to-agent (skill) communication and regular channel communication.

Changes:

• Added ResolveConnectorClientScopes method to determine appropriate OAuth scopes based on the activity's recipient role
• Modified ProcessActivityAsync to use the new scope resolution logic instead of always using AgentClaims.GetTokenScopes
• Added comprehensive test coverage for all scope resolution scenarios

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/libraries/Builder/Microsoft.Agents.Builder/ChannelServiceAdapterBase.cs	Implements conditional scope resolution logic that uses BotFramework scope by default and agent appId scope only for Skill role
src/tests/Microsoft.Agents.Builder.Tests/ChannelServiceAdapterBaseTests.cs	Adds three test cases covering non-skill role, skill role with agent ID, and skill role without agent ID scenarios

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tracyboehrer]

@sw-joelmut We can hold on this for now. We will need to revisit concerning the teams client, but since that is getting changed soon, we can wait.