.NET: Re-enable AzureAI.Persistent packaging and integration tests

[rogerbarreto]

Motivation and Context

Azure.AI.Agents.Persistent 1.2.0-beta.10 now targets Microsoft.Extensions.AI 10.4.0+, resolving the compatibility issue (McpServerToolApprovalResponseContent → ToolApprovalResponseContent rename) that required disabling this package from NuGet shipping and its integration tests.

Closes #4769

Description

• Removed <IsPackable>false</IsPackable> from Microsoft.Agents.AI.AzureAI.Persistent.csproj to re-enable NuGet packaging
• Re-enabled all 6 integration test classes by changing [Trait("Category", "IntegrationDisabled")] → [Trait("Category", "Integration")] and removing the associated disable comments
• Removed the outdated compatibility warning section from README.md

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the Contribution Guidelines
• All unit tests pass, and I have added new tests where possible
• Is this a breaking change? If yes, add "[BREAKING]" prefix to the title of the PR.

[Copilot]

Pull request overview

Re-enables packaging and CI integration testing for the Microsoft.Agents.AI.AzureAI.Persistent .NET integration layer now that Azure.AI.Agents.Persistent has updated compatibility with Microsoft.Extensions.AI 10.4.0+.

Changes:

• Re-enabled NuGet packaging for Microsoft.Agents.AI.AzureAI.Persistent by removing the IsPackable=false override.
• Re-enabled Azure AI Persistent integration test classes by switching their test category trait back to "Integration".
• Removed the now-obsolete compatibility warning block from the package README.

Reviewed changes

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

Show a summary per file

File	Description
dotnet/src/Microsoft.Agents.AI.AzureAI.Persistent/Microsoft.Agents.AI.AzureAI.Persistent.csproj	Allows the project to be packable again for NuGet shipping.
dotnet/src/Microsoft.Agents.AI.AzureAI.Persistent/README.md	Removes outdated compatibility limitation content.
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentCreateTests.cs	Re-enables integration test class via trait change.
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentRunTests.cs	Re-enables integration test class via trait change.
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentRunStreamingTests.cs	Re-enables integration test class via trait change.
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentStructuredOutputRunTests.cs	Re-enables integration test class via trait change (but current logic still skips tests).
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsChatClientAgentRunTests.cs	Re-enables integration test class via trait change.
dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsChatClientAgentRunStreamingTests.cs	Re-enables integration test class via trait change.

Comments suppressed due to low confidence (1)

dotnet/tests/AzureAIAgentsPersistent.IntegrationTests/AzureAIAgentsPersistentStructuredOutputRunTests.cs:12

• SkipReason is a non-null const string, so Assert.SkipWhen(SkipReason is not null, ...) will always evaluate true and these structured-output integration tests will always be skipped even after re-enabling the [Trait("Category", "Integration")] category. If these tests are meant to run again, make the skip conditional (e.g., based on an env var/CI detection) or remove the overrides and let the base tests execute; if they must stay disabled, consider marking them with an explicit xUnit Skip attribute or reverting this class back to an IntegrationDisabled category to avoid giving a false sense of coverage.

[Trait("Category", "Integration")]
public class AzureAIAgentsPersistentStructuredOutputRunTests() : StructuredOutputRunTests<AzureAIAgentsPersistentFixture>(() => new())
{
    private const string SkipReason = "Fails intermittently on the build agent/CI";