Remove AWS Device Farm benchmark jobs

[GregoryComer]

Summary

Take down the AWS device farm benchmarking jobs. We are dropping them due to performance data being unreliable on non-rooted devices.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• ROCm failures during provisioning step due to network issues

✅ No Failures

As of commit 81b815a with merge base 2cafc34 ():
💚 Looks good so far! There are no failures yet. 💚

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[GregoryComer]

Note: I'm dropping the build-benchmark-app jobs, since they're built per benchmark run. If we want to keep those, I can move them to pull/trunk jobs to make sure they build. Let me know and I'll do that.

[GregoryComer]

@mergennachin are we ready to take down the benchmark jobs?