[Misc][MoE] add Deepseek-V3 moe tuning support

[divakar-amd]

• add moe tuning support for DeepSeek-V3
• add arg.trust_remote_code for better user exeperience. Use --trut_remote_code when tuning for deepseek

Currently, DeepSeek-V3 runs into error when using graph-mode. This has been handled by forcing 'eager-mode' as a workaround. Hence, bypassing graph capture in the moe tuning script for deepseek-v3
- use a boolean variable use_graphs to selectively diasble graph capture for DeepSeek-V3
- get_default_config was missing is_marlin flag. Set it to False as default.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
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 do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[tlrmchlsmth]

Thank you for the contribution. This looks good to me.

Note: I ran into a couple of somewhat orthogonal issues when trying it out, so threw up #12562 to address them

[mgoin]

LGTM for this part, but we still need to add support for the block fp8 config