Enable aarch64 CPU performance benchmarks

[ioana-ghiban-arm]

Purpose

This PR aims to fix #26019

Reiterating on the explanation from pytorch-integration-testing PR:

PyTorch already have G3 runners (see https://hud.pytorch.org/runners/pytorch?search=m7g).
This patch lets us leverage those in the vLLM benchmark dashboard,
on the same model that's used to measure x86 performance.

Test Plan

Functionally, the changes in implementation and testing are the same as the PR to enable vLLM BMs for Intel CPUs

Test Result

TBD

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• [] The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors.

You ask your reviewers to trigger select CI tests on top of fastcheck CI.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

If you have any questions, please reach out to us on Slack at https://slack.vllm.ai.

🚀