Reenable android arm32 tests

[vitek-karas]

Enables back tests on Android arm32. This fixes #125440 .
The real fix was creation of a new Android queue with devices which support arm32 on-device emulation. The larger Android queue is now used only for arm64 runs and all the devices in it support that architecture.
The new queue is small (only 10 devices), but the amount of tests running on it will be small as well.

[dotnet-policy-service]

Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

This PR updates the Azure Pipelines platform matrices to re-enable Android arm32 (android_arm) test legs for Mono-based Android device runs, both in the main runtime pipeline and in the extra-platforms Android pipeline.

Changes:

• Re-add android_arm to the Android devices platform list in eng/pipelines/runtime.yml.
• Re-add android_arm to the Android devices platform list in eng/pipelines/extra-platforms/runtime-extra-platforms-android.yml.

Reviewed changes

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

File	Description
eng/pipelines/runtime.yml	Re-enables android_arm in the Mono Android devices matrix for the main runtime pipeline.
eng/pipelines/extra-platforms/runtime-extra-platforms-android.yml	Re-enables android_arm in the Mono Android devices matrix for the extra-platforms Android pipeline.

[vitek-karas]

/azp run runtime-android

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[vitek-karas]

/azp run runtime-android

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[vitek-karas]

Note

This comment was AI-generated by Copilot from the rerun logs and issue state, then reviewed before posting.

I re-checked the rerun of runtime-android (Build 1436900). The failures still look like pre-existing Android test buckets rather than anything introduced by this PR.

This PR only changes pipeline YAML to re-enable the Android arm32 legs:

• eng/pipelines/runtime.yml
• eng/pipelines/extra-platforms/runtime-extra-platforms-android.yml

Bucket	Tracking	Why it isn't PR-related
System.Net.NameResolution localhost-subdomain address-family mismatch	#128371	Existing Android resolver/test failure in unrelated test code; it repros across arm/arm64 lanes and is independent of this queue/YAML change.
System.Net.Sockets ConnectAsync_WithBuffer_Succeeds	#125825	Long-running Android sockets assertion failure; this PR does not touch System.Net.Sockets or the tests.
NativeAOT System.Net.Sockets Connection reset by peer / Connect_ExposeHandle_FirstAttemptSucceeds	#122493	Existing Android NativeAOT sockets bucket; again unrelated to the PR's pipeline-only changes.
System.Security.Cryptography.Tests Android JNI / RSA app crash	#128660	Newly tracked Android crypto crash; the PR does not touch crypto/native implementation, only re-enables these runs.

The earlier System.Security.Cryptography.Csp.Tests discovery bucket did not repro in this rerun.

So the rerun still shows Android coverage issues, but they appear to be pre-existing test/platform problems surfaced by re-enabling the arm32 jobs, not regressions caused by this PR.

[vitek-karas]

/ba-g all the unmatched failures are dead-lettered osx jobs. Since this change only enabled Android queue testing, the osx validation is not necessary.