[release/8.0-staging] [PERF] Update Perf Android jobs to use the Windows 11 Pixel Queue.

[github-actions]

Backport of #95614 to release/8.0-staging

/cc @LoopedBard3

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #95614 to release/8.0-staging

/cc @LoopedBard3

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[LoopedBard3]

@carlossanlop I have this infra-only update for release 8, 7, and 6 staging to update one of the queues we use. Can I get this approved and merged for each? The other backports are #95656 and #95657. Also, we will be doing more of this in the semi-near future so please let me know if there is a different way we should go about these backports. Thanks!

[carlossanlop]

Tell-mode. Approved.
@LoopedBard3 do you have permission to merge? The release/X.0-staging branches should not be restricted like the release/X.0 ones (but maybe it's just for maintainers).

[carlossanlop]

And to answer your question: This is the right way to do it, target the release/X.0-staging branches. If you don't have permission to merge, that's ok, just ping me or anyone in the @dotnet/runtime-infrastructure group and we can merge it for you.

[LoopedBard3]

Looks like I do have merge permission. Thanks for the help!