[V0 Deprecation] Remove unused context_len and seq_len from M-RoPE

[DarkLight1337]

Purpose

From my understanding, these arguments are only passed in V0, as the slicing is now handled by model runner inside V1, so we can remove this from modeling code.

Test Plan

Test Result

---

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.

[gemini-code-assist]

Code Review

This pull request removes the unused context_len and seq_len arguments from get_mrope_input_positions across multiple model files, which is a good cleanup as part of the V0 deprecation. The changes are mostly consistent and correct.

However, I've found two critical issues that need to be addressed:

1. The SupportsMRoPE protocol in vllm/model_executor/models/interfaces.py still defines context_len and seq_len in its get_mrope_input_positions signature. This protocol should be updated to match the new function signatures in the implementing classes to avoid signature mismatches.
2. In vllm/model_executor/models/qwen3_omni_moe_thinker.py, only the function signature was updated, but the usage of context_len and seq_len within the function body appears to have been missed. This will likely cause a NameError at runtime.

Please address these issues to ensure the correctness and consistency of the codebase.

[DarkLight1337]

/gemini review

[gemini-code-assist]

Code Review

This pull request aims to remove the unused context_len and seq_len arguments from get_mrope_input_positions functions across multiple models, which is a good cleanup. The changes are mostly correct and consistent. However, I've found a critical issue in qwen3_omni_moe_thinker.py where removing seq_len from the function signature without updating its usage in the function body will lead to a runtime error. Please address this to ensure the code remains functional.