[release/8.0] Remove unsupported mobile queues from .NET 8 extra-platforms CI

[Copilot]

main PR N/A — .NET 8 servicing-only CI configuration change.

Description

.NET 8 mobile targets are out of support, but the extra-platforms pipeline still scheduled Android/mobile legs that can fail on unsupported TLS 1.1 behavior.

• Removed mobile template inclusions from runtime-extra-platforms.yml:
  • Android device/emulator
  • iOS/tvOS device/simulator
  • Mac Catalyst
• Left non-mobile extra-platform coverage unchanged.

Customer Impact

Reduces unsupported .NET 8 mobile CI noise blocking servicing flow validation.

Regression

No. This removes unsupported CI coverage rather than changing product behavior.

Testing

YAML-only change; validated by targeted inspection.

Risk

Low. The change only stops the aggregate extra-platforms pipeline from including unsupported mobile queues.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

• Fixes [Android] SslStreamTls11NetworkConformanceTests fail with 'SslProtocols (Tls11) are not supported on this platform' despite ConditionalClass(SupportsTls11) skip #133998

[azure-pipelines]

Azure Pipelines:
16 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

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

[rzikm]

@copilot This PR targets main but the instruction explicitly said that the PR should target release/8.0-staging

[Copilot]

@copilot This PR targets main but the instruction explicitly said that the PR should target release/8.0-staging

I verified PR #134037 is currently based on main. The required fix is to retarget the PR base to release/8.0-staging; this is PR metadata, and I don’t have an available safe tool here to update the base branch directly. No repository file change is needed for this comment.

[rzikm]

@copilot I retargeted the PR to release/8.0-staging, you need to rebase the changes to that branch as well so that we don't include unrelated commits

[rzikm]

@copilot I retargeted the PR to release/8.0-staging, you need to rebase the changes to that branch as well so that we don't include unrelated commits

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

[Copilot]

@copilot I retargeted the PR to release/8.0-staging, you need to rebase the changes to that branch as well so that we don't include unrelated commits

I recreated the branch locally on top of origin/release/8.0-staging; the intended result is single commit d667c693c3 containing only the mobile queue removal. I could not publish it from this environment: the available progress tool repeatedly rebases against the old origin/copilot/fix-android-sslstreamtls11-tests main-based history before pushing, causing broad unrelated conflicts, and I’m not allowed to force-push the rewritten branch directly.

[rzikm]

I can't update the branch (the ref is not visible), so I will raise PR manually