.NET: Address Integration Concurrency Tests failure for V2 Agents

[rogerbarreto]

Motivation and Context

When using V2, multiple integration tests running concurrently may delete existing agent instances still running and this can lead to 404 problems.

The fix adds the missing agent random naming for the specific crafted integration tests for the V2 agents that were missing this update.

Fixes

• https://github.com/microsoft/agent-framework/actions/runs/19634066317/job/56220447791

[Copilot]

Pull request overview

This PR fixes integration test concurrency issues for V2 Agents by ensuring each test creates uniquely named agent instances, preventing 404 errors when concurrent tests attempt to delete shared agents.

• Made GenerateUniqueAgentName method public for reuse across test classes
• Updated four integration test methods to use dynamic unique agent names instead of hardcoded constants

Reviewed changes

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

File	Description
AIProjectClientFixture.cs	Changed GenerateUniqueAgentName visibility from private to public to allow external test classes to generate unique agent names
AIProjectClientCreateTests.cs	Updated four test methods (CreateAgent_CreatesAgentWithCorrectMetadataAsync, CreateAgent_CreatesAgentWithVectorStoresAsync, CreateAgent_CreatesAgentWithCodeInterpreterAsync, CreateAgent_CreatesAgentWithAIFunctionToolsAsync) to use dynamically generated unique agent names instead of hardcoded constant names, preventing concurrency conflicts