[CI] Upgrade vllm to 0.11.1

[wxsIcey]

What this PR does / why we need it?

Upgrade vllm to 0.11.1

• Fix AscendScheduler post_init, caused by [Bugfix]: Clean up chunked prefill logging when using whisper vllm#25075
• Fix AscendScheduler init got an unexpected arg block_size, caused by [bugfix][DCP] fix block_size of hash in DCP prefix caching vllm#26296
• Fix KVCacheManager get_num_common_prefix_blocks arg, caused by fix(v1/kv_cache): resolve async KV transfer bug in cascade attention vllm#23485
• Fix MLAAttention import,caused by Separate MLAAttention class from Attention vllm#25103
• Fix SharedFusedMoE import, caused to [Model] Apply shared experts overlap optimization to all models with shared experts vllm#26145

Does this PR introduce any user-facing change?

N/A

How was this patch tested?

CI passed with new added/existing test.

• vLLM version: v0.11.0rc3
• vLLM main: https://github.com/vllm-project/vllm/commit/v0.11.0

[github-actions]

👋 Hi! Thank you for contributing to the vLLM Ascend project. The following points will speed up your PR merge:‌‌

• A PR should do only one thing, smaller PRs enable faster reviews.
• Every PR should include unit tests and end-to-end tests ‌to ensure it works and is not broken by other future PRs.
• Write the commit message by fulfilling the PR description to help reviewer and future developers understand.

If CI fails, you can run linting and testing checks locally according Contributing and Testing.

[wxsIcey]

Upgrade vllm to newest commit: #3423

[gemini-code-assist]

Code Review

This pull request upgrades vllm to version 0.11.1 and adapts the vllm-ascend codebase to the API changes. The changes correctly address several breaking changes in the new version. However, I've found a critical issue with the version checking mechanism. The function vllm_version_is performs an exact version match, which is not robust for ensuring compatibility across different vllm versions. This could lead to runtime errors if used with versions other than the exact ones specified. This issue is present in multiple files and needs to be addressed to ensure the code is resilient to version changes.