Run iPhone benchmark on private devices

[huydhn]

Same as #10192, but this is for the private iPhone 15 devices. I will need to follow on this with another PR to get the device pool name / id and maybe the device id

Testing

https://hud.pytorch.org/benchmark/llms?startTime=Wed%2C%2016%20Apr%202025%2004%3A22%3A32%20GMT&stopTime=Wed%2C%2023%20Apr%202025%2004%3A22%3A32%20GMT&granularity=day&lBranch=apple-private-devices&lCommit=be72291c9b643581fedafaf8711d07fd5542b62d&rBranch=apple-private-devices&rCommit=be72291c9b643581fedafaf8711d07fd5542b62d&repoName=pytorch%2Fexecutorch&benchmarkName=&modelName=All%20Models&backendName=All%20Backends&modeName=All%20Modes&dtypeName=All%20DType&deviceName=All%20Devices&archName=All%20Platforms

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/10380

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 3 New Failures

As of commit ea1cab8 with merge base 59870c5 ():

NEW FAILURES - The following jobs have failed:

• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / test-eval_llama-mmlu-linux / linux-job (gh)
  RuntimeError: Command docker exec -t e6523a477faa4feac31208923ec59f6d22a22eb2d2b06366517d8e8757958fe2 /exec failed with exit code 1
• trunk / test-llama-runner-mac (fp32, coreml) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[guangy10]

iOS 15. Is it a typo, you mean iOS 18?

[huydhn]

iOS 15. Is it a typo, you mean iOS 18?

Yeah, we have iPhone 15 iOS 18 and iPhone 15 iOS 17.2.1

[huydhn]

After looking at the test run on the dashboard. The devices shows up as Apple iPhone 15 (iOS 18.0) and Apple iPhone 15 Pro Max (iOS 17.2.1) which couldn't be separate from the regular public iOS devices. I will land this but disable the schedule for now to avoid confusion when this runs in main. I'll work on adding the device pool ID & device ID and enable the workflow on that PR.