[release/10.0] [PERF] Remove hybrid globalization from iOS perf scenarios

[github-actions]

Backport of #119399 to release/10.0

/cc @LoopedBard3 @matouskozak

Customer Impact

• Customer reported
• Found internally

No customer impact, impacts the performance pipelines. (https://dev.azure.com/dnceng/internal/_build/results?buildId=2801881&view=results)

Regression

• Yes
• No

Caused by the general updates made to the performance flow here: dotnet/performance#4933

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

Low due to being an infra/yml fix that impacts only the performance pipelines, which have failures due to not having this update.

[dotnet-policy-service]

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

[LoopedBard3]

FYI @matouskozak @caaavik-msft

@AaronRobinsonMSFT Is merging into release/10.0 currently the correct approach for backporting to net10.0? If so, can I get it looked at and merged? Let me know if there is a different process I should follow. Thanks.

[AaronRobinsonMSFT]

@AaronRobinsonMSFT Is merging into release/10.0 currently the correct approach for backporting to net10.0? If so, can I get it looked at and merged? Let me know if there is a different process I should follow. Thanks.

Yes, it is the correct branch to target. Let me ping you offline and go over the process.

[JulieLeeMSFT]

Please get code review.

[caaavik-msft]

Approving.

My only comment is that by changing the artifact names it prevents us from being able to run performance tests against runtime commit versions that used the old artifact name. As a separate piece of work we should figure out how to remove this coupling so that the artifacts and their names can change independently of the test suite.