Add fused MoE kernel tuning configs (fp8_w8a8) for DeepSeek V3/R1 on a single-node 8x NVIDIA H20 96GB setup

[sunyicode0012]

Add fused MoE kernel tuning configs (fp8_w8a8) for DeepSeek V3/R1 on a single-node 8x NVIDIA H20 96GB setup
#5196
Fused MoE kernel configuration tuned on a single-node system with 8× NVIDIA H20 GPUs
The command used is:
python benchmark_moe.py
--model /datacenter/model/DeepSeek-R1/
--trust-remote-code
--dtype fp8_w8a8
--tp-size 8
--tune

[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 can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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.

🚀

[sunyicode0012]

Warning messages appear during the execution of the vLLM server when running inference for DeepSeek V3/R1 on a single-node system with 8× H20 GPUs.

After applying the configuration：

[mergify]

⚠️ The sha of the head commit of this PR conflicts with #18337. Mergify cannot evaluate rules on this PR. ⚠️