[TrimmableTypeMap] Integration parity tests

[simonrozsival]

Stacked on #10823.
Part of #10798

Scope

• Integration test project setup
• UserTypes fixture assembly used by parity tests
• Side-by-side scanner parity tests against legacy behavior
• CI wiring for integration test execution

Review guide

Two commits — review in order:

1. Integration parity test slice — test project, UserTypes fixture, and scanner comparison tests
2. Wire integration tests into solution and CI — .sln entries, CI yaml, InternalsVisibleTo

[Copilot]

Pull request overview

Adds an integration test slice for TrimmableTypeMap scanner parity by building a real-user-types fixture assembly and running side-by-side comparisons against the legacy Cecil-based scanner, then wires these integration tests into the solution and Windows CI.

Changes:

• Add Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests project with scanner parity/comparison tests (Mono.Android + user fixture).
• Add UserTypesFixture project to produce a “real user types” assembly referencing Mono.Android/Java.Interop.
• Wire the integration tests into Xamarin.Android.sln, add InternalsVisibleTo, and run/publish results in the Windows CI steps.

Reviewed changes

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

Show a summary per file

File	Description
tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/UserTypesFixture/UserTypesFixture.csproj	New fixture project that compiles user-type edge cases and outputs DLL next to integration tests.
tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/UserTypesFixture/UserTypes.cs	User-type fixture source covering component attributes, nested types, [Export], etc.
tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/ScannerComparisonTests.cs	New parity tests comparing legacy scanner output vs new SRM-based scanner across multiple dimensions.
tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/MockBuildEngine.cs	Minimal IBuildEngine stub for TaskLoggingHelper usage in scanner tests.
tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests.csproj	New xUnit integration test project referencing TrimmableTypeMap + Build.Tasks + fixture build output.
src/Xamarin.Android.Build.Tasks/Properties/AssemblyInfo.cs	Adds InternalsVisibleTo for the new integration test assembly.
build-tools/automation/yaml-templates/build-windows-steps.yaml	Runs/publishes TrimmableTypeMap integration tests in Windows CI.
Xamarin.Android.sln	Adds the new integration test and fixture projects to the solution.

[simonrozsival]

/azp run Xamarin.Android-PR

[azure-pipelines]

No pipelines are associated with this pull request.

[simonrozsival]

/azp run Xamarin.Android-PR

[azure-pipelines]

No pipelines are associated with this pull request.

[jonathanpeppers]

This one fails to build with:

(CoreCompile target) -> 
         /Users/runner/work/1/s/android/tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/ScannerComparisonTests.Helpers.cs(138,3): error xUnit2020: Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead. (https://xunit.net/xunit.analyzers/rules/xUnit2020) [/Users/runner/work/1/s/android/tests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests/Microsoft.Android.Sdk.TrimmableTypeMap.IntegrationTests.csproj]

    296 Warning(s)
    1 Error(s)