add cuda benchmark ci

[Gasoonjia]

Summary: Introduce cuda benchmark ci for monitoring cuda backend performance.

the ci will run on three situations:

1. it will run all possible models (voxtral, gemma and whisper) combine with all possible quantization schema on every day's 1am pst;
2. it will run an random model everytime a PR got merged;
3. manually tirggered by user.

Differential Revision: D87400561

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (4 Unrelated Failures)

As of commit b991c34 with merge base b4d72f1 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / unittest-editable / linux / linux-job (gh) (similar failure)
  exir/backend/test/test_lowered_backend_module.py::TestBackendAPI::test_emit_nested_lowered_backend_module
• trunk / test-qnn-optimum-model (fp32, cvt) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / linux / linux-job (gh) (trunk failure)
  exir/backend/test/test_lowered_backend_module.py::TestBackendAPI::test_emit_nested_lowered_backend_module
• trunk / unittest-release / linux / linux-job (gh) (trunk failure)
  exir/backend/test/test_lowered_backend_module.py::TestBackendAPI::test_emit_nested_lowered_backend_module

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

[meta-codesync]

@Gasoonjia has exported this pull request. If you are a Meta employee, you can view the originating Diff in D87400561.

[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.

[Gasoonjia]

Address comments, show gpu name on dashboard, support running all tests on script

[Gasoonjia]

update dashborad content to make it more descriptive.

[meta-codesync]

@Gasoonjia has imported this pull request. If you are a Meta employee, you can view this in D87400561.