Update fp4 quantize API

[wenscarl]

Update fp4 quantize API

cc. @alexm-redhat

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.

Purpose

Test Plan

Test Result

(Optional) Documentation Update

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

🚀

[gemini-code-assist]

Code Review

This pull request updates the FlashInfer FP4 quantization API by renaming fp4_swizzle_blockscale to nvfp4_block_scale_interleave and updating a function call in flashinfer_cutlass_moe to use keyword arguments. The code changes are consistent across the modified files and improve readability. A significant concern is the absence of tests to validate these changes. Modifying low-level quantization kernels without corresponding tests introduces a high risk of regressions. It is highly recommended to add unit or integration tests that specifically exercise the FP4 MoE functionality with the updated FlashInfer API to ensure the integration is correct and robust.

[alexm-redhat]

LGTM, thanks for the quick fix!