[Android] Run CoreCLR library tests on Android

[kotlarmilos]

Description

This PR enables running CoreCLR library tests on the Android emulators and devices and adds a script for local testing on Windows.

Changes

• Disabled library tests that require assemblies on disk
• Disabled library tests that are failing on CoreCLR Android
• Re-enabled passing tests on Android
• Added a script for local testing on Windows

Disabled tests fall into two categories.

Globalization or other mobile‐platform issues

These tests have been disabled because they depend on invariant‐culture behaviors or platform APIs that aren’t fully supported on mobile targets:

System.Runtime\tests\System.Globalization.Tests\Invariant\Invariant.Tests.csproj
System.Net.Http\tests\FunctionalTests\System.Net.Http.Functional.Tests.csproj
System.Diagnostics.DiagnosticSource\tests\TestWithConfigSwitches\System.Diagnostics.DiagnosticSource.Switches.Tests.csproj
System.Reflection.MetadataLoadContext\tests\System.Reflection.MetadataLoadContext.Tests.csproj
System.Runtime\tests\System.Resources.ResourceManager.Tests\System.Resources.ResourceManager.Tests.csproj
System.Runtime\tests\System.Runtime.Tests\InvariantTimezone\System.Runtime.InvariantTimezone.Tests.csproj
System.Runtime.Loader\tests\System.Runtime.Loader.Tests.csproj
System.Runtime\tests\System.Text.Encoding.Tests\System.Text.Encoding.Tests.csproj
System.Runtime\tests\System.IO.Tests\System.IO.Tests.csproj
Microsoft.Bcl.Cryptography\tests\Microsoft.Bcl.Cryptography.Tests.csproj
System.Net.Security\tests\FunctionalTests\System.Net.Security.Tests.csproj
System.Net.WebSockets\tests\System.Net.WebSockets.Tests.csproj

CoreCLR Android-specific failures

The following disabled tests are specific to CoreCLR Android:

Microsoft.VisualBasic.Tests.ErrObjectTests.Clear
MonoTests.System.Configuration.mapped_ExeConfiguration_null
MonoTests.System.Configuration.OpenExeConfiguration1_UserLevel_None
System.Threading.Tests.MutexTests - add a process-wide implementation of named mutex to CoreCLR on Mono to better compatibility with Mono
System.IO.Pipelines.Tests.CompleteWithLargeWriteThrows

Closes #50871 #50874 #50923 #49937 #114148

[kotlarmilos]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

This PR is ready to be merged.

/cc: @steveisok Build machines run out of disk space without symbol stripping. Enabling symbol stripping makes the app non-debuggable and breaks adb shell run-as access to internal storage where test results are stored. For test infrastructure, we need both: debuggable builds and stripped binaries. I created tracking issue that will be done as follow-up: #115717

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

/azp run runtime-android,runtime-androidemulator

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kotlarmilos]

Follow-up work tracked in #114951 and #115717.