Update new fixed-AR-MTP CI workflow for kimik2.5_int4, kimik2.5_fp4, …

[haic0]

[Summary] Implemented and validated CI support for the new Eagle3 and fixed-AR MTP benchmark paths.

For amd-master.yaml, added matrix coverage for:

kimik2.5-int4-mi355x-vllm-eagle3
kimik2.5-mxfp4-mi355x-vllm-eagle3
minimaxm2.5-fp8-mi355x-vllm-eagle3
kimik2.5-int4-mi355x-vllm-fixed-ar-mtp
kimik2.5-fp4-mi355x-vllm-fixed-ar-mtp
Added benchmark scripts for:

Kimi INT4 Eagle3
Kimi FP4/MXFP4 Eagle3
MiniMax FP8 Eagle3
Kimi INT4 fixed-AR MTP
Kimi FP4 fixed-AR MTP
MiniMax FP8 Eagle3 fixed-AR support
Updated CI workflow plumbing:

Added fixed-ar-mtp scenario support in matrix validation and generation.
Updated e2e-tests.yml to route fixed-AR MTP jobs through benchmark-tmpl.yml.
Updated benchmark-tmpl.yml to pass draft model, speculative token count, rejection method, and synthetic acceptance rates into benchmark scripts.
Updated launch_mi355x-amds.sh to resolve Eagle3 and fixed-AR MTP script names correctly.
Added mtp-fixed-ar-amd.yml for LiveCodeBench-based synthetic acceptance-rate generation.
Installed and ran actionlint; fixed workflow lint issues.
Validation completed:

[github-actions]

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

• https://docs.sglang.io/cookbook/intro
• https://recipes.vllm.ai/

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

• https://github.com/vllm-project/recipes
• https://github.com/sgl-project/sglang/tree/main/docs_new

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.