add parakeet into cuda benckmark ci

[Gasoonjia]

Stack from ghstack (oldest at bottom):

• -> add parakeet into cuda benckmark ci #17182

as title

Differential Revision: D92208958

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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, 4 Unrelated Failures

As of commit 443bcc2 with merge base fdb386c ():

NEW FAILURES - The following jobs have failed:

• Lint / link-check / lint-file-size / linux-job (gh)
• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t cf97a1d7787cfbcf3d6d33aefdb4f53c7ebc5c318111ce56dbfada9b5cbbe786 /exec failed with exit code 1
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 7bb03d0a6d58acef245f01a27e6a36cae41d7c5f57febc349357cc0b5f3c649c /exec failed with exit code 1

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / unittest / macos / macos-job (gh) (similar failure)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

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

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

• pull / test-samsung-models-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-samsung-quantmodels-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)
  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.

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