Corrected OBO echange failed message

[tracyboehrer]

Fixes #344

[Copilot]

Pull Request Overview

This pull request addresses issue #344 by correcting the error messages shown when an OBO exchange fails. The key changes include:

• Modifying the exception creation in AzureBotUserAuthorization.cs to use a simplified scopes representation.
• Updating the error message in Resources.resx to provide additional troubleshooting guidance.

Reviewed Changes

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

File	Description
src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/AzureBotUserAuthorization.cs	Updated exception formatting to use the 'scopes' parameter.
src/libraries/Builder/Microsoft.Agents.Builder/Properties/Resources.resx	Expanded error message text for OBO exchange failures.

Files not reviewed (1)

• src/libraries/Builder/Microsoft.Agents.Builder/Properties/Resources.Designer.cs: Language not supported

Comments suppressed due to low confidence (2)

src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/AzureBotUserAuthorization.cs:128

• Verify that 'scopes' is always properly initialized and handles null or empty cases, as the previous version explicitly indicated a null value when necessary.

                    throw Core.Errors.ExceptionHelper.GenerateException<InvalidOperationException>(ErrorHelper.OBOExchangeFailed, ex, [connectionName, string.Join(",", scopes)]);

src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/AzureBotUserAuthorization.cs:134

• Ensure that the use of 'scopes' without an explicit null check retains the intended clarity from the previous implementation, especially when token acquisition returns null.

                    throw Core.Errors.ExceptionHelper.GenerateException<InvalidOperationException>(ErrorHelper.OBOExchangeFailed, null, [connectionName, string.Join(",", scopes)]);